chore: cut v0.6.1 (second cut) - #379
Merged
Merged
Conversation
…on evidence iss-289 resolves (the toolchain pin shipped). The three issues stranded in the superseded cut branch re-mint as iss-326/327/328 after the live id collision with the bughunt session's iss-291..293 — itself captured as iss-330, direct field evidence for itd-114. iss-329 records Go 1.25 leaving the support window. itd-93's fold references move to the new ids and iss-327 carries the promoted_to stamp. Assisted-by: Claude:claude-fable-5
…unt round The composed section (launch ship --changelog-json) cites every in-changelog record of the cut: the release-toolchain pin (iss-289), the guard short-flag-cluster fix, the ParseSemver range guard, the wording corrections, and the record catch-up sweep (iss-291..300, bughunt round 1). The hand-written Unreleased prose those fixes carried moves into the composed section per the cutover contract, which requires an empty Unreleased; the 0.6.0 section's triplicate iss-268 entry and the reference README's phantom pages are fixed per the prior gate's dispositions, re-verified by the fresh gate run this branch's receipts commit records. Assisted-by: Claude:claude-fable-5
Both host-run gates ran fresh and full-tier against the re-cut content commit dc4de34 — nothing reused from the superseded cut, whose tree lacked the bughunt round-1 changes. docs-currency: PROMOTE, zero findings, the superseded review's three fixes verified in this tree and every entry of both newest CHANGELOG sections exercised live against the binary. iss35 crosscheck: PROMOTE, 37 brief-drift findings, all dispositioned to iss-328's chapter-by-chapter sweep — consistent across both runs and the v0.5.1 precedent. The release job's exact receipt gate ran 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 | e065818 | Aug 20 2026, 05:45 AM |
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, rebuilt after the parallel-mint id collision (iss-330) superseded #378. Three commits: the record set (iss-289 resolve, the re-minted iss-326/327/328, iss-329 Go-line EOL, iss-330 collision evidence, itd-93 reference fixes), the roll (content commit
dc4de34), and the receipts naming it — the gate arms atHEAD^2^= the roll, receipts in the tagged tree.## [0.6.1] - 2026-08-20, composed over ten records: the release-toolchain pin (iss-289) plus bughunt round 1 (guard short-flag-cluster bypass iss-291, ParseSemver range guard iss-293, wording fixes iss-294/295, the record catch-up sweep iss-296..300). Bughunt's hand-written Unreleased prose moved into the composed section per the cutover contract.dc4de34: docs-currency PROMOTE, zero findings (prior fixes verified, both newest sections exercised live against the binary); iss35 crosscheck PROMOTE, 37 brief-drift findings dispositioned to iss-328's sweep — consistent across runs.What merging does
auto-release tags v0.6.1 at this merge, verify runs, the receipt gate finds both PROMOTE receipts in the tagged tree, and the run pauses at the
releaseenvironment for the maintainer's approval — the click that publishes the first release of the 0.6 line, built on Go 1.25.13. v0.6.0 stays tagged-unpublished (iss-326).Assisted-by: Claude:claude-fable-5