Repository navigation
Skip the burned v0.1.1-v0.1.2 and retract v0.1.0-v0.1.2 - #123
Merged
Merged
Conversation
Those versions were published from history rewritten on 2026-11-13, so the Go proxy and sum.golang.org serve code git no longer holds. release-please's next version is 0.1.3 and go.mod retracts the range; a test keeps both.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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
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.
Summary
release-please-config.jsonsetsrelease-as: 0.1.3for the next release.src/go.modretracts[v0.1.0, v0.1.2]; the retraction takes effect when v0.1.3 is published.TestNextReleaseSkipsTheBurnedVersionschecks both; it was seen failing withrelease-asset to 0.1.1 and with the retract range cut to v0.1.1.No tag is pushed by this change.