Skip to content

chore(release): date 0.7.0 - #36

Merged
jonyoder merged 1 commit into
mainfrom
chore/release-0.7.0
Aug 14, 2026
Merged

chore(release): date 0.7.0#36
jonyoder merged 1 commit into
mainfrom
chore/release-0.7.0

Conversation

@jonyoder

Copy link
Copy Markdown
Collaborator

Dates [Unreleased] as 0.7.0 (2026-08-14) and adds its compare link.

Verified against git diff v0.6.0..origin/main -- CHANGELOG.md that the section contains exactly the one subheading added since that tag (### Addedversion.ReleaseKey), so no already-published content is re-dated.

Also corrects that entry's opening line before it becomes immutable. It said ReleaseKey.String "renders the smallest version string carrying a key", which is false in the way that matters: it renders the shortest one, and 1.0a1 and 1.0.dev0 carry the same key while sorting strictly below it. A paragraph further down in the same entry already says exactly that, so the summary line contradicted its own body. It also said "group", which reads as "map key" — a ReleaseKey holds a slice and cannot be one.

A Go module tag is immutable once the proxy has served it, so a wrong claim here would only be fixable by a further release.

🤖 Generated with Claude Code

Dates [Unreleased] as 0.7.0 (2026-08-14) and adds its compare link.
Verified against `git diff v0.6.0..origin/main -- CHANGELOG.md` that the
section contains exactly the one subheading added since that tag, so no
already-published content is re-dated.

Also corrects that entry's opening line before it becomes immutable. It
said ReleaseKey.String "renders the smallest version string carrying a
key", which is false in the way that matters: it renders the SHORTEST
one, and 1.0a1 and 1.0.dev0 carry the same key while sorting strictly
below it. The paragraph further down already says so; the summary line
contradicted it. It also said "group", which reads as "map key" — a
ReleaseKey holds a slice and cannot be one.
@jonyoder
jonyoder merged commit 096bd91 into main Aug 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant