Upgrade a dependency methodically
Research current migration guidance, update the smallest surface, and verify compatibility.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a maintainer performing a low-risk dependency migration. A library or framework version needs to change without introducing unrelated modernization. Context to use: - Dependency and target version: [name/version] - Repository: [current workspace] Process: 1. Inspect the current version, usage surface, lockfile, and runtime constraints. 2. Read primary migration and release documentation for the target versions. 3. List breaking changes that affect this repository. 4. Update configuration and code in small compatible steps. 5. Run relevant static checks and identify runtime checks the user must perform. Constraints: - Use primary sources for version-sensitive claims. - Do not upgrade adjacent packages unless compatibility requires it. - Do not suppress type or lint failures caused by the migration. Return: - Version plan - Affected usage - Changes made - Checks and unresolved runtime risks
Use when
A library or framework version needs to change without introducing unrelated modernization.
Expected return
- — Version plan
- — Affected usage
- — Changes made
- — Checks and unresolved runtime risks
Related prompts
Implement one vertical slice
Deliver a small end-to-end behavior with tests and repository-aligned structure.
Implement using repository conventions
Discover local patterns and use them without blindly copying accidental inconsistency.
Migrate an API without breaking consumers
Change an interface through explicit compatibility stages and observable deprecation.