dependency-upgrade

To safely upgrade project dependencies, this skill isolates security patches, minor updates, and major version bumps into distinct, bisectable commits. It enforces reading changelogs and running automated tests to ensure system stability throughout the upgrade process.

Yes, you can apply security patches separately. The upgrade workflow categorizes security patches, minor updates, and major version changes into isolated, verifiable commits, allowing you to address vulnerabilities independently of larger version bumps.

The best way to audit dependencies across npm, pip, and cargo is using an automated workflow that reviews changelogs and migration guides. This process categorizes necessary updates and mandates linting, building, and full test suite execution after every step.

To verify project stability after a major dependency version bump, the workflow mandates reading migration guides before applying changes, followed by strict linting, building, and full test suite execution to ensure the project remains in a green state.

Dependency updates should be separated into distinct commits to create a bisectable history that isolates breaking changes. This structured workflow mitigates risks by ensuring each security patch, minor update, or major version change is individually verifiable through automated tests.

Yes, you need to read changelogs before applying major version dependency updates. The upgrade workflow enforces strict adherence to reviewing changelogs and migration guides prior to major version changes to prevent runtime breakage and maintain stability.