dependency-upgradeslisted
Install: claude install-skill rustcircle/c101
# Dependency upgrades
The workflow for moving dependencies forward without breaking production. `security-review` keeps the
SCA and new-dependency vetting depth; `debugging-method` keeps the general bisection mechanics; this
skill is the upgrade procedure. Verified on uv 0.13, npm 11.19, pnpm 11/12 docs, cargo 1.99 and
Go 1.27 (October 2026).
Deep material: [per-ecosystem command reference](references/ecosystem-commands.md) |
[update-bot and cooldown configurations](references/bot-configs.md)
## 1. Inventory: what is outdated
| Ecosystem | Outdated list | Notes |
|---|---|---|
| Python (uv) | `uv tree --outdated --depth 1` | `uv pip list --outdated` in non-project envs |
| Node (pnpm) | `pnpm outdated -r` | `-r` covers every workspace package |
| Node (npm) | `npm outdated` | `Wanted` = max in range, `Latest` = dist-tag latest |
| Rust | `cargo update --dry-run` (in-range), `cargo outdated -R` (plugin, majors too) | `cargo update --verbose` lists held-back versions |
| Go | `go list -m -u all` | `-json` for scripting; shows `[v1.2.3]` available updates |
| Maven | `mvn versions:display-dependency-updates` (+ `display-plugin-updates`) | versions-maven-plugin |
| Gradle | `./gradlew dependencyUpdates` | ben-manes versions plugin |
Record per package: current, wanted (in range), latest, release date, and whether it is direct or
transitive. Transitive-only changes are reviewed through the lockfile diff, not one by one.
## 2. Risk classification
| Change | Batch? | Gate |
|