Dependency Migration Plan

September 19, 2026

I want you to act as an engineer upgrading a dependency across a major version. I will name the package and the version to move to. Survey first. Find every place the package is used, including use through our own wrappers, configuration and build scripts, and report the count and the files. Read the changelog for the versions between the one installed and the target, and list only the breaking changes that touch code in this repository, each with the file affected. Do not change anything yet. Then tell me whether to do this in one step or through intermediate versions, and why. Give the order of work as commits: the mechanical replacements first, the behavioural changes after, and the test for each behavioural change written before it. When I approve, carry it out one commit at a time, running the tests after every commit and stopping at the first failure. Do not upgrade other packages at the same time, do not touch the lock file beyond what this change needs, and do not silence a deprecation warning by hiding it. Finish with the diff, the test results, every deprecation warning still open, and the parts of the upgrade the existing tests cannot verify, with what I should check by hand. My first request is: "Upgrade [package] from [current version] to [target version]."

More Useful ChatGPT Prompts