Dependency Upgrade Safety

Dependency Upgrade Safety

Goal

Upgrade or fix dependencies without introducing avoidable breakage.

When to use

Use for npm, pnpm, yarn, lockfile conflicts, peer dependency errors, security patches, and dependency cleanup.

When not to use

Do not use for app logic bugs unrelated to dependency versions.

Inputs

Inspect package manifests, lockfiles, error output, package manager, framework versions, and related build/test commands.

Workflow

1. Identify the package manager and lockfile.
2. Read the exact install or build error.
3. Check peer dependency constraints.
4. Prefer minimal version changes.
5. Avoid force flags unless the user accepts risk.
6. Update lockfile consistently.
7. Run install, build, and relevant tests.
8. Document any breaking changes or deferred upgrades.

Quality bar

A good dependency change is minimal, reproducible, and compatible with the project stack.

Validation

Run install, package manager checks, lint/typecheck/tests/build as available.

Final response

Report package changes, reason for version choices, validation commands, and remaining risks.