Repository navigation
[Docs] Say release tags and releases can't change once published - #19
Merged
Merged
Conversation
Since 2026-10-13 a ruleset blocks updating or deleting v* tags for everyone, admins included, and releases are immutable from v0.3.1 on: tag and files locked, title and notes editable. GoReleaser 2.18.3 uploads to a draft and publishes last, so a failed upload leaves a draft, not a partial release. AGENTS.md now says both, so agents don't try to move a tag or rebuild a release. Co-Authored-By: Claude Opus 5.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.
Opus 5.5 Max wrote this:
Tell agents that release tags and releases can no longer change once published, so they don't try to move a tag or rebuild a release. Follow-up of #18.
Set on 2026-10-13 in the repo settings, not in this diff:
refs/tags/v*, rulesupdate,deletionandnon_fast_forward, no bypass. Creating tags stays allowed, which CI needs. Its first evaluation, a no-op update of v0.3.0 to the commit it already points at, matched the tag and ran all 3 rules as active against an admin; they passed because nothing moved.internal/client/github.go: "Always start with a draft release while uploading artifacts"), so it works with immutable releases. A failed upload leaves a draft, not a partial release, which is what AGENTS.md now says.Merging releases nothing.
release-tag.shon this commit, dry run:Not released: nothing that ships changed since v0.3.0, only docs, tests or CI. This is the first real run of that path.