Dependency Upgrade Plan
By Rania · Published · Updated
Sequences a set of dependency upgrades from safest to riskiest, summarises the breaking changes in each, and defines the checks to pass before moving on.
Prompt template
## Dependency Upgrade Plan Plan the upgrade of these dependencies. - Dependencies and versions: [textarea: Name then current version then target version for each] - Project type: [text: Node API or Flutter app or Django site] - Test coverage: [dropdown: Strong, Patchy, Almost none] - Deployment risk: [dropdown: Internal tool, Customer facing, Revenue critical] - Release notes or changelogs: [textarea: Paste anything relevant or leave blank] - Time available: [text: One afternoon or two sprints] Group the packages into those that depend on each other and those that stand alone. Order the upgrades so the foundations come first (runtime, language, build tool), then shared libraries, then leaf packages, and do patch and minor bumps before majors. For each major, list the breaking changes from the notes supplied, the code areas likely to feel them, and what to search for in the codebase. Mark anything you cannot confirm from the notes as a thing to verify, never as fact. After every step define the checks: install, build, tests, type checks, and one manual smoke test, with a clear rule for rolling back to the last good commit. Recommend one pull request per step for risky upgrades and a combined one for safe patches. Finish with the first three steps to do today.