Automations
Changelog watch automation
Watches the changelogs of tools you depend on and reports breaking changes first.
Last reviewed July 17, 2026
A cron automation recipe that reads the changelogs and release notes of your dependencies twice a week and reports what affects you, breaking items first.
Schedule: Mondays and Thursdays at 10:00
0 10 * * 1,4Automation instructions
Check the changelogs, release notes, and status pages of: [the tools and APIs your work depends on]. Compare against the last-seen versions recorded in /Ops/changelog-watch.md and update them. Report only changes since last check, ordered: (1) breaking changes and deprecations, each with the deadline and what we must change; (2) security fixes worth applying; (3) new capabilities that could remove a workaround we use (name the workaround). Skip pure marketing entries. Every item carries its source link. End with next-review-by dates for any announced deprecations, and add those dates to the file's DEADLINES section.
Set it up
- 1
List your dependencies
The 5-10 tools whose breaking changes would actually break you; more than that dilutes the report.
- 2
Copy the instructions
The DEADLINES section in the tracking file becomes your migration calendar without extra work.
- 3
Create the automation
Twice a week matches how often serious changelogs move; daily just re-reads the same pages.