Add release TODO checks to the release script - #2945
Merged
Conversation
Manual steps around a production deploy (migrations, load balancer or Cloud Run settings, secrets, follow-up scripts) were easy to forget because the release script only looked at package versions. - .release-todos/<pr>-<name>.md files with optional '## before' and '## after' sections; shown at the start / after the deploy PR merge, then deleted on the release branch - automatic listing of new migration files since the last deploy - TODO_RELEASE marker grep, scoped to git diff master...staging - collected items become the body of the 'Deploy latest to production' PR Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
marcocastignoli
approved these changes
Aug 27, 2026
marcocastignoli
left a comment
marcocastignoli
left a comment
Member
There was a problem hiding this comment.
I didn't test it, but I think this is a very clean solution!
github-project-automation
Bot
moved this from Sprint - Needs Review
to Sprint - Done
in Sourcify Public
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Manual steps around a production deploy were easy to forget, because the release script only looked at package versions. Migrations are applied by hand, and the "Deploy latest to production" PR had an empty body. See the discussion on #2937 (drop
idx_code_code_first_75).This adds
scripts/release/release_todos.sh, wired intomain.sh:.release-todos/<pr-number>-<short-name>.mdfiles with optional## beforeand## aftersections.beforeitems are shown at the start of the release,afteritems once the deploy PR is merged. The script deletes the files on the release branch, so the directory only holds open items.TODO_RELEASEmarkers in added lines are listed as a safety net.Everything is scoped to
git diff master...staging, so an item shows up for exactly one release.Notes
.release-todos/README.mddocuments the format.services/database/README.mdandCLAUDE.mdnow say that every migration PR must add such a file..release-todos/file. Can follow in a separate PR.🤖 Generated with Claude Code