release: 1.0.0 - #68
Merged
Merged
Conversation
The version the binary reports, which the release workflow refuses a tag that disagrees with, so this lands before v1.0.0 is pushed. 1.0 is a promise rather than a milestone: breaking changes start costing a major bump. docs/compatibility.md says what that covers and, more usefully, what it does not -- diagnostic wording above all, since the characterization suite records every message exactly and a reworded error is indistinguishable in a diff from a behavior change. The promise is worth making now because there is nothing outstanding. The 25-issue backlog is cleared, the two gaps the pre-1.0 audit turned up are fixed, both remaining issues are closed, and Known Gaps holds one entry that is a performance question rather than a semantic one. What made it enforceable rather than aspirational: 226 characterization cases, 141 README code blocks and 20 examples, all executed, so a change that breaks a documented program cannot land quietly. CLAUDE.md's tag example follows the constant, and the pretty-print example's sample config named the old version in data that reads as this project's own. The tag has to be v1.0.0. The workflow accepts an unprefixed one for the sake of the old tags, but the module proxy does not, and an unprefixed tag is why `go install github.com/fadion/aria@latest` spent years resolving to a 2017 pseudo-version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The version the binary reports. The release workflow refuses a tag that disagrees with
const version, so this lands beforev1.0.0is pushed.1.0 is a promise rather than a milestone: breaking changes start costing a major bump. docs/compatibility.md says what that covers and, more usefully, what it does not.
It's worth making now because nothing is outstanding — the 25-issue backlog is cleared, the pre-1.0 audit's findings are fixed, both remaining issues are closed, and Known Gaps holds one entry that is a performance question rather than a semantic one.
What changed
const versioninaria.go, from0.6.0to1.0.0.CLAUDE.md's tag example, so it follows the constant.pretty-printexample's sample config, which named the old version in data that reads as this project's own, plus its golden.Tagging
The tag has to be
v1.0.0. The workflow accepts an unprefixed tag for the sake of the pre-0.6 ones, but the module proxy does not — an unprefixed tag is whygo install github.com/fadion/aria@latestspent years resolving to a 2017 pseudo-version.226 characterization cases, 141 README blocks, 20 examples, all green.