CodingText outputStructured Data outputCode outputAdvanced

Plan a Safe Dependency Upgrade

Identifies breaking changes, affected code, migration steps, tests, rollout risks, and rollback criteria.

Published by AIPM · Updated Sep 5, 2026 · 0 copies

Ready to use

Prompt

Plan a safe dependency upgrade using the supplied project and version context.

Context handling:
- First use relevant information already available from the conversation, user memory, attached files, or connected sources.
- Do not ask the user to repeat information you already have.
- Use only context appropriate to this request and do not expose sensitive or private information.
- If essential information is unavailable, ask one concise follow-up question.
- State important assumptions and never invent facts.

Input:
{{upgrade_context}}

Produce:
1. Scope and assumptions
2. Breaking-change inventory
3. Affected code and transitive dependencies
4. Incremental migration sequence
5. Required configuration and code changes
6. Test plan
7. Observability and rollout
8. Rollback criteria
9. Documentation updates

Requirements:
Verify unstable version-specific details against official release notes when browsing is available. Never invent APIs or breaking changes.

Create your final prompt

Add your context and generate

Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.

{{upgrade_context}}RequiredCurrent and target dependency versions plus relevant manifests, code, or release notes.

What to expect

Example output

An incremental migration plan with tests, rollout safeguards, and rollback criteria.

Example context

Example input

Provide current and target versions with manifests and relevant configuration.

Discussion

Comments (0)

Loading comments…