c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.3 KiB
1.3 KiB
Safely update project dependencies with compatibility verification.
Steps
- List all outdated dependencies:
npm outdated,pip list --outdated. - Categorize updates by risk:
- Patch: Bug fixes, safe to auto-update.
- Minor: New features, backward compatible.
- Major: Breaking changes, requires review.
- For each update candidate:
- Read the changelog for breaking changes.
- Check peer dependency compatibility.
- Verify TypeScript type compatibility if applicable.
- Apply updates in order: patch first, then minor, then major.
- After each batch, run the test suite.
- If tests fail, identify the breaking dependency and provide fix guidance.
- Update lock file and commit changes.
Format
Dependency Updates Applied:
Patch (safe):
- <pkg> 1.0.0 -> 1.0.1
Minor (compatible):
- <pkg> 1.0.0 -> 1.1.0
Major (breaking - review required):
- <pkg> 1.0.0 -> 2.0.0: <breaking change summary>
Tests: <pass/fail after updates>
Rules
- Never update major versions without reading the changelog first.
- Run tests after each update category, not just at the end.
- Commit patch and minor updates separately from major updates.
- Do not update dev dependencies and production dependencies in the same batch.
- Keep a rollback plan: note the exact versions before updating.