dep-upgradelisted
Install: claude install-skill ychampion/ystack
# Dependency upgrade
Bumping everything at once turns ten small breakages into one knot nobody can untangle. Upgrade one
thing, prove it, keep it, move on.
## When it applies
- Several outdated or vulnerable packages to bring up to date.
- A single major-version upgrade (a framework, a compiler, a runtime).
- Merging a backlog of automated bump PRs.
## Procedure
### 1. Baseline
On a clean branch, run install, build, type check, lint and tests. Record what passes now. A test that
already fails is not the upgrade's fault; note it and keep it out of the verdicts.
### 2. List and order
Use the ecosystem's own tool (`bun outdated`, `pnpm outdated`, `pip list --outdated`,
`cargo outdated`, `go list -m -u all`, `npm audit` / `pip-audit` for vulnerabilities). Order:
1. security fixes;
2. patch and minor bumps, batched only if they're in the same family;
3. majors, one per step, low-level ones (runtime, compiler, test runner) before the things on top.
Packages that must move together (a framework and its plugins, a type package and its library) are
one step.
### 3. Read before you bump
For each major, read the changelog or migration guide between the current and target version. Note
every breaking change, then search the code for each removed or renamed API. If the list is long,
split the upgrade into a prep step (adapt the code on the old version where possible) and the bump.
### 4. Bump one step
Change the one version, install, and let the lockfile update. Check the lo