Repository navigation
Add a Claude skill for cutting State Tool releases - #3861
Open
icanhasmath wants to merge 4 commits into
Open
icanhasmath wants to merge 4 commits into
icanhasmath wants to merge 4 commits into
Conversation
Records the release flow (master after the last beta merge-back -> release branch -> beta -> release), the changelog convention, and the post-merge staging, Windows signing, S3 promotion and merge-back steps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closed
Releases continue the last RC branch with cherry-picks from master; they are not cut from master or beta. Records the protected version branches, the beta sync merge, the CI failures hit on 0.48.2 and their fixes, the Trivy scan gate, CI tooling quirks, and the S3 checks. Steps after the beta merge are marked unverified. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From 0.48.2-RC2: cutting a fix-up RC from beta's tip, re-signing it, testing encrypted private ingredients with a key contract, CVEs that keep arriving during a release, and the macOS socket-path failure on long branch names.
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
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.
Adds
.claude/skills/release-state-tool/SKILL.md, the release procedure as learned while cutting 0.48.2-RC1 (PROD-240). It's separate from the release PRs.Steps 0–10 were all done for real on the 0.48.2 beta (#3863, #3865, #3866, #3864, then staging, signing, promote and verify, 2026-10-23 to 10-26). Two things haven't been run with it yet: the merge back into
masterand the stable (beta → release) path.What it records:
version/0-48-1-RC4+version.txtbump =version/0-48-2-RC1) and cherry-pick themasterchanges that ship. Don't mergemaster, which has drifted, and don't branch frombeta.master's first-parent commits since the lastMerge branch 'version/...', notbeta..master.version/*is protected: direct pushes and "Update branch" are refused, so every change goes in as a PR.beta: a PR that mergesbetain, merged with a merge commit, so the release PR isn't BEHIND. The release PR itself is squash-merged, so each release repeats this.internal/hailTestOpen flake.-RCn(0.48.2-SHA89954c6).info.jsonfiles, since the updater checks it. Remove TI'ssign/folder before promoting.betacheckout after generating the constants (otherwise it fails withundefined: constants.ChannelName). It moves everything understaging/.-vet=off, running Trivy locally) and CI tooling quirks.