dependency-upgradelisted
Install: claude install-skill tmj-90/gaffer
# Upgrade a dependency safely
A dependency change imports someone else's decisions into your build. Treat it like a
code change from a stranger: read what changed, run everything that could be affected,
keep the lockfile honest, and never "bump and hope".
**Gaffer constraints — read first.**
- Your delivery prompt forbids installing, updating or removing dependencies in any
ecosystem; that needs human approval. The safety hook enforces it for
`npm|pnpm|yarn install|i|add|ci|update|up|upgrade|remove|rm|uninstall` and
`pip install`. Do not look for a command that dodges the hook (bare `yarn`,
`bun install`, `uv sync`, `poetry add`, `bundle install`, `go get`, `cargo update`
are equally off-limits), and never hand-edit a lockfile to fake one.
- In a delivery worktree `node_modules` is a symlink to the main checkout's install.
Never run `npm ci`, `pnpm install`, `update` or `prune` there: it rewrites or empties
the shared install and breaks every other worktree.
- Consequence: your tests run against the version that is ALREADY installed, not the
one in your edited manifest. Check which version actually ran
(`node -p "require('<pkg>/package.json').version"`, `pip show <pkg>`, `go list -m <mod>`)
before claiming the new version is tested.
## Steps
1. **Pin down the reason.** A security advisory (which CVE/GHSA, which versions are
fixed), a feature you need, or hygiene. The reason sets the minimum target and does not
license unrelated bumps. For an adv