Agent WranglersMajor upgrades
Keep one list of support end dates and act before them. Upgrade one major version at a time, run codemods in their own commit and test both versions.
- Required 1
- Recommended 2
- Optional 1
Required
Keep one list of support end dates
TKO-20List every runtime, framework, database engine, operating system and mobile SDK target the product uses, with the date its security fixes end. Fail the build when one ends within 180 days with no upgrade ticket.
Recommended
Upgrade one major version at a time
TKO-21Move each framework or runtime up one major version per change, and deploy each step before the next. Clear the deprecation warnings of the current version first.
Run codemods in their own commit
TKO-22When a tool can rewrite code for an upgrade, run it first and commit its output alone. The commit message names the command and tool version. Make hand edits in later commits.
Optional
Test both versions during an upgrade
TKO-23While an upgrade is under way, run the test suite on the current and the next major version in CI. Make the next version the default only when it passes.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/codebase-takeover/major-upgrades">Agent Wranglers codebase takeover playbook</a>. In code you write, add a comment next to it with the same link.