-
v0.40.1
StableAll checks were successfulchangelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 6scheck-self-bootstrap / check (pull_request) Has been skippedchangelog-body-check / check (pull_request) Successful in 0sfragment-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 5sfragment-check / changelog fragment-kind (pull_request) Successful in 11sfragment-check / check (pull_request) Successful in 0sgo-ci / lint + build + test (pull_request) Successful in 21smanifest-check / manifest-vs-tag consistency (pull_request) Successful in 7smanifest-check / check (pull_request) Successful in 0sregister-check / register-drift check (pull_request) Successful in 7sregister-check / check (pull_request) Successful in 0stests / bats (pull_request) Successful in 22stests / shellcheck (pull_request) Successful in 7scheck-self-bootstrap / check (push) Successful in 5sgo-ci / lint + build + test (push) Successful in 43srelease / decide + act (push) Successful in 10srelease / release (push) Successful in 0stests / bats (push) Successful in 23stests / shellcheck (push) Successful in 7sgoreleaser / build + publish rt asset (push) Successful in 1m28smirror-on-cut / mirror-1 (release) Successful in 1smirror-on-cut / mirror (release) Successful in 0sreleased this
2026-08-19 10:23:44 +02:00 | 824 commits to main since this releaseAdded
None.
Changed
None.
Fixed
A failed cut can no longer stamp the same version twice. Both changelog emit paths now refuse a
## [X.Y.Z]heading the file already carries, naming the existing section's line number.The state this catches is stamped-but-uncut: a cut stamps the version, fails before tagging, then the next run sees no tag and stamps again. The duplicate is dangerous rather than untidy. Everything extracting a version's section takes the first match and stops, so the second block is dropped silently while the file still parses and every gate passes.
The post-cut manifest check can read the default branch again. Its fetch ran without credentials, so it reported the branch unreadable and refused a cut that had in fact succeeded.
The branch read now happens in the workflow step, which holds a credential, and the result is passed to
rt manifest-postcondition. The decision is unchanged. Readable-and-absent stays distinct from unreadable: only the first is evidence, so an unreachable branch still refuses to grade rather than convicting a cut.- release: the readable-and-absent path aborted before rt was called
Removed
None.
Deprecated
None.
Upgrade
None.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads