Plan a safe dependency update
Plans a dependency update in small batches from your outdated list, with the risky packages isolated and a rollback step for each batch.
Task:
Plan how I update the outdated dependencies below in numbered batches, with a rollback step for each batch.
Context:
The project is [language and framework] with the package manager [package manager]. The tests are [what tests exist and how long they take]. I can spend about [time available] on this, and the lockfile is committed in [version control system].
Rules:
- Read the list before planning and group packages that depend on each other.
- Put packages with a major version jump in their own batch and say what usually breaks there. Tell me to check each changelog, since you cannot be sure of the details.
- Start with the batch that is safest and easiest to roll back.
- Before suggesting any command that deletes the lockfile or the installed packages, or that forces a push, explain what it removes.
- Ask for no tokens or private registry credentials in the chat.
Result:
A numbered list of at most 6 batches. Each batch has the packages, the risk in one word, the commands to run and the rollback step.
Material:
[paste the outdated packages list here]