chore(release): prepare v0.14.10 (supersedes the orphaned v0.14.9 tag) - #274
Merged
Conversation
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
v0.14.9 was tagged and pushed, and the Release workflow failed at the Test Gate: hack/verify-doc-facts.sh requires every git tag >= v0.7.0 to have a "## vX.Y.Z" CHANGELOG header, and none existed. GoReleaser never ran, so no artifacts were published for that tag. Rather than move a pushed ref, this cuts v0.14.10 with the same contents and leaves v0.14.9 in place. The gate enumerates git tags, not published releases, so the orphaned tag needs a CHANGELOG entry permanently; it gets a short stub recording that it was never published and pointing at v0.14.10. - CHANGELOG: v0.14.10 entry (contents of #270, #271, #272) + v0.14.9 stub - internal/buildinfo/version.go -> 0.14.10 - docs/current-state.md regenerated - the three summary goldens embed the version string and move with it Process note: there are two documentation gates, and release prep for v0.14.9 ran only verify-repo-truth.sh. Both verify-repo-truth.sh and verify-doc-facts.sh must be green before tagging. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
toasterbook88
changed the title
toasterbook88
force-pushed
the
chore/changelog-v0.14.8-v0.14.9
branch
from
August 4, 2026 04:04
7de0d37 to
5bb907a
Compare
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.
Cuts v0.14.10. Supersedes the
v0.14.9tag, which was pushed but never published.What happened
v0.14.9was tagged and the Release workflow failed at the Test Gate:hack/verify-doc-facts.shrequires every git tag>= v0.7.0to have a## vX.Y.Zheader. GoReleaser never ran — no artifacts exist for that tag.Release prep for v0.14.9 ran
verify-repo-truth.shand notverify-doc-facts.sh. There are two documentation gates; both must be green before tagging.Why v0.14.10 rather than moving the tag
Moving a pushed ref was the alternative. Cutting a new version touches no existing ref. The gate enumerates git tags, not published releases, so
v0.14.9will require a CHANGELOG entry permanently — it gets a short stub recording that it was never published and pointing here.Changes
CHANGELOG.md—v0.14.10entry covering test: self-isolate the two tests that depended on the caller for HOME #270, feat(install): install system-wide by default and harden the replacement path #271, test(fleet): add a write-containment guard and a two-node facts smoke test #272, plus thev0.14.9stubinternal/buildinfo/version.go→0.14.10docs/current-state.mdregeneratedVerification
Next
Merge, then
git tag v0.14.10 && git push origin v0.14.10.🤖 Generated with Claude Code