dependency-upgrade

To safely upgrade dependencies, you should separate low-risk patches from high-risk major updates. This skill plans dependency upgrades in risk-based batches, requiring verification and testing between each group to catch regressions early.

The best way to handle major package upgrades is to isolate them from minor updates. This skill scopes the impact of major version migrations, reads changelogs, and documents deferred work to ensure breaking changes are managed safely.

Yes, you can batch dependency upgrades by risk level for Node, Python, Rust, Ruby, and Go projects. The process separates dev dependencies, runtime patches, and major updates so the safest package upgrades land first.

Fixing security vulnerabilities safely requires applying patched updates in isolated batches. This skill executes dependency upgrades incrementally, verifying builds and tests after each batch to avoid bundling multiple breaking changes into a single commit.

If a major dependency upgrade breaks build verification, you should isolate the change and review the package changelog. This skill isolates major-version migrations and documents deferred work to handle breakage without halting low-risk upgrades.