modules: bury the mistaken v1.0.0 with a v1.0.1 retraction shim - #13
Merged
Conversation
Retraction is read from the highest version's go.mod. v1.0.0 (1.0.0 > 0.2.4) outranks our real release, and its old go.mod has no retract — so 'go install @latest' still resolved to v1.0.0 and failed to build. Fix per the Go modules playbook for a mistaken high tag: retract v1.0.0 AND a new higher v1.0.1 from this go.mod, then tag v1.0.1. With the highest version self-retracted, @latest falls to v0.2.4. The release workflow now triggers on v0.* only, so the v1.0.1 shim tag publishes no binaries and doesn't touch the Homebrew formula. Co-Authored-By: Claude Fable 5 <[email protected]>
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 retract-only fix didn't work: Go reads retractions from the highest version's go.mod, which is
v1.0.0(1.0.0 > 0.2.4) — and its old go.mod has no retract. Sogo install @lateststill resolved to v1.0.0 (and failed to build).Standard Go fix for a mistaken high tag: retract v1.0.0 and v1.0.1 from this go.mod, then tag
v1.0.1. With the highest version self-retracted,@latestfalls tov0.2.4.release.ymlnow triggers onv0.*only → the v1.0.1 shim tag builds no GitHub release and doesn't bump the Homebrew formula.v1.0.1(git tag only) and verifygo install …@latest→ 0.2.4.go vetclean,go mod verifyok, builds.🤖 Generated with Claude Code