Back to prompt library

Plan a low-risk dependency upgrade

Your dependencies are old and you're afraid to upgrade in case something breaks.

When to use it Before you upgrade dependencies

What you get

A dependency upgrade plan you can roll out in batches.

Before you start

  • The project has a dependency manifest and a lockfile

Steps

  1. Identify the runtime and package manager
  2. Group into direct dependencies, build tooling and security fixes
  3. Check for breaking changes and Node version requirements
  4. Plan per-batch verification and rollback

Deliverables

  • Upgrade batches
  • Risk table
  • Verification commands

Done when

  • Each batch has its own verification step
  • No unrelated refactoring is mixed in

Paste this into your agent

Do a read-only analysis of dependency upgrades for this project. Identify the runtime, package manager, lockfile and CI; split the upgrades into batches by risk and coupling, and list breaking changes, verification commands and rollback points. Do not install or change any dependencies. Stop once you've produced the above; don't go on to anything else.