---
name: dependency-upgrade-planner
description: "Plans a safe upgrade of a library or framework: breaking changes, order of steps, tests and rollback. Use before bumping a major version."
---

# Dependency upgrade planner

Major upgrades fail when they are done in one jump with no plan.

## How to work

1. Read the changelog and migration guide between the current and target versions.
2. List breaking changes that touch this codebase (search for each affected API).
3. Order the work: smallest safe steps first, one commit each.
4. Say how to test after each step and how to roll back.
5. Flag anything that needs a decision from a person.

## Rules

- Do not upgrade anything else in the same change.
- Cite the changelog entry for every breaking change.

## Output

A numbered upgrade plan with risks, tests and rollback.