Framework Version Upgrade Plan
Plan an upgrade across breaking changes with testing steps.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan an upgrade from [CURRENT_VERSION] to [TARGET_VERSION] of [FRAMEWORK]. Project size and key features used: [PROJECT_DETAILS]. Dependencies: [DEPENDENCIES]. Test coverage: [TEST_COVERAGE]. Ask me to supply the official upgrade guide or release notes, and use them rather than memory; list any breaking changes you cannot confirm [VERIFY]. Plan in stages: read notes, update dependencies in small groups, fix compile errors, fix deprecations, run tests, manual test of critical paths, staged rollout. Return a stage table with Task, Risk, Check and Time, a rollback plan, a list of dependencies that may block the upgrade, and the branch strategy. Estimate effort as a range and explain what makes it larger. Provide a step-by-step example with a small invented project: update the runtime first, then the framework's patch version, then the minor version, then the major version, running tests between steps. Describe how to use a compatibility table, codemods if the project provides them, and a branch that is merged frequently with the main line to avoid a huge final merge. Include a checklist for the day of the upgrade deployment and a contingency if production behaves differently from staging. Add a communication note to the team about a freeze on unrelated dependency changes during the work. List documentation to update afterwards, such as setup instructions and onboarding material.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.