Goal
Upgrade with no surprises in production: every breaking change found before release, every step small enough to revert.
Inputs
- Framework or library and versions: [e.g. Laravel 9 to 11, Node 18 to 22]
- Dependency file: [paste package.json, composer.json, requirements.txt or similar]
- Code samples that use the framework heavily: [paste key files or describe usage]
- Test coverage: [e.g. good unit tests, few tests, none]
- Release process: [e.g. staging then production, direct deploy]
Steps
- List the breaking changes between the two versions that are known to you, and tell the user to confirm each against the official upgrade guide.
- Match each change to the code samples given, or mark it "search the codebase for X".
- Find other dependencies that must upgrade at the same time.
- Order the work into small steps, such as one intermediate version at a time.
- Write the test and rollback plan.
Output format
- | Breaking change | Where it affects the code | Fix | Effort (S, M, L) |
- Dependencies to upgrade together, with target versions to verify.
- Upgrade sequence, numbered.
- Test plan: automated tests, manual checks of key user flows, performance check.
- Rollback plan in three lines.
Check before answering
- Version numbers and changes you are unsure of are marked "verify in the release notes".
- No step mixes the upgrade with new features or refactoring.
- Security advisories fixed by the upgrade are mentioned only if known, never guessed.
- The plan works with the test coverage stated, adding tests where coverage is weak.






