wowprompt

Dependency upgrade plan for a major framework version

Plans a major upgrade of a framework or library, such as a new React, Laravel, Django or Node version, with breaking changes mapped to your code and a staged rollout. Use it before an upgrade that has been postponed for too long and now blocks security fixes.

A table of breaking changes matched to affected files with effort, an ordered upgrade sequence, a test plan and a rollback plan
The output this prompt produced, unedited.

The prompt

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

  1. 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.
  2. Match each change to the code samples given, or mark it "search the codebase for X".
  3. Find other dependencies that must upgrade at the same time.
  4. Order the work into small steps, such as one intermediate version at a time.
  5. 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.
dependency upgradeframework upgradebreaking changesmajor version upgradeupgrade checklisttechnical debt

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity