chore: cut v0.6.1 - #378
Closed
REPPL wants to merge 3 commits into
Closed
Conversation
The derived cut: base v0.6.0, next v0.6.1, decided by iss-289 (resolved in this commit). The dated section is the first composed through launch ship --changelog-json — one Fixed entry citing iss-289, the completeness bijection over the cut's record set. v0.6.0 remains tagged but unpublishable (iss-291): its tree carries no semantic receipts and the re-release path builds only from the tagged commit, so this cut supersedes it as the first published release of the 0.6 line. Assisted-by: Claude:claude-fable-5
Both host-run gates ran full-tier against the content commit c4a09af: docs-currency (pristine worktree, every docs/ page and README plus the two newest CHANGELOG sections claim-by-claim against the built binary) and the iss-35 brief-surface crosscheck (the pinned manifest's 22 checkers, both directions). Both PROMOTE. The docs findings are fixed here per their dispositions — the two superseded iss-268 changelog drafts deleted, the reference README's phantom pages corrected; the crosscheck's 37 brief-drift findings are captured to iss-293 for a chapter-by-chapter sweep rather than buried in a release branch. The release job's exact receipt gate was run locally against this tree before push: exit 0. Assisted-by: Claude:claude-fable-5
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
abcd | dc767cd | Aug 20 2026, 05:25 AM |
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Aug 19, 2026
REPPL
enabled auto-merge
August 19, 2026 22:06
Collaborator
Author
|
Superseded by the re-cut: this branch's content commit minted iss-291/292/293 concurrently with the bughunt session's identically-numbered issues (the id collision is captured as iss-330, live evidence for itd-114), and receipts are sha-bound, so the cut is rebuilt from current main — richer for it: the new record set carries the toolchain pin plus bughunt round 1 (iss-289, iss-291..300). The replacement PR follows once the re-run gates PROMOTE. Assisted-by: Claude:claude-fable-5 |
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
1 participant
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.
What
The v0.6.1 cut, in the runbook's exact two-commit shape:
c4a09af— resolves iss-289 (the release-toolchain pin) and writes## [0.6.1] - 2026-08-19, the first section composed throughlaunch ship --changelog-json(one Fixed entry, bijection over the cut's record set).What merging does
auto-release tags v0.6.1 at this merge; the gate arms at
HEAD^2^= c4a09af, finds both receipts in the tagged tree, verify runs, and the release pauses at the environment for the maintainer's approval. v0.6.0 stays tagged-unpublished (iss-291); this is the first published release of the 0.6 line, built on the pinned Go 1.25.13.Assisted-by: Claude:claude-fable-5