dependency-upgradelisted
Install: claude install-skill Kuan-AI-com/agent-skills
# Upgrade a dependency
## 1. Know where you are and where you go
- Current version from the lockfile (the installed one, not only the range in the manifest) and the target version. If the user said "latest", look it up and state the exact number.
- The package manager and its version (npm, pnpm, yarn, pip, poetry, uv, bundler, cargo, go).
- Why: security fix, needed feature, end of support. It decides how far to go.
## 2. Read before touching
- The changelog and the official migration guide for every major version between current and target. Do not skip intermediate majors: their breaking changes still apply.
- Peer dependencies and plugins that must move together (types packages, framework plugins, lint configs).
- The minimum runtime version the new release needs.
- Codemods the maintainers publish. Prefer them to manual edits.
- If you cannot open the changelog, say so and work from compiler errors and tests, flagging that behaviour changes may be missed.
## 3. Get a baseline
Run the test suite, type check, lint and build on the current version first. Record what already fails so you do not blame the upgrade for it.
## 4. Upgrade in steps
- One major version at a time for big jumps. One package (or one group that must move together) per commit.
- Update with the package manager so the lockfile changes properly. Do not hand-edit lockfiles.
- After each step: install, build, type check, tests. Fix what breaks before going further.
- Search the code for every removed