deepsource-mcp-server: Command for Claude Code

Update Dependencies

You are about to update the dependencies of the project. This command helps maintain the project's dependencies while adhering to the established CI/CD workflow and changeset requirements.

Workflow Steps

1. Create a Feature Branch

Create a new branch following the naming convention:

git checkout -b chore/update-dependencies-<date>
# Example: chore/update-dependencies-2024-01

2. Update Dependencies

For Production Dependencies:

# Check outdated packages
pnpm outdated

# Update all dependencies to latest
pnpm update --latest

# Or update specific packages
pnpm update <package-name> --latest

For Dev Dependencies:

# Update dev dependencies
pnpm update --latest --dev

3. Install and Lock Dependencies

# Ensure pnpm-lock.yaml is updated
pnpm install

# Deduplicate dependencies if needed
pnpm dedupe

4. Test the Updates

Run the full verification suite to ensure compatibility:

# Run all checks (audit, typecheck, lint, format, test)
pnpm verify

# Run specific checks if needed
pnpm test
pnpm typecheck
pnpm lint

5. Create a Changeset

IMPORTANT: The CI/CD pipeline requires changesets for all changes. Choose the right type based on impact:

When to Use Empty Changeset

Use pnpm changeset --empty for changes that don't affect users:

• Dev dependency updates only
• CI/CD configuration changes
• Test-only improvements
• Internal tooling updates
• Documentation changes

# Create an empty changeset (no version bump)
pnpm changeset --empty

# The changeset message should document:
# - Which dependencies were updated
# - Why they were updated
# - Any tooling changes developers should know about

When to Use Regular Changeset

Use pnpm changeset for changes that affect the package/application:

• Production dependency updates
• Security fixes visible to users
• Breaking changes in dependencies
• Bug fixes from dependency updates
• New features from dependency updates