Fix release workflow to work with immutable releases setting#1650
Merged
Conversation
A repo setting change enabled immutable releases, which prevents uploading assets to a release once it's published. Creating the release as a draft here lets goreleaser upload all assets first, then publish as its final step. Change-Type: fix Release-Note: no Audience: internal Impact: medium Breaking: false Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
needs triage
tashian
approved these changes
Jun 10, 2026
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
4 participants
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.
A repo setting change enabled immutable releases, which prevents uploading assets to a release once it's published. Creating the release as a draft lets goreleaser upload all assets first, then publish as its final step.
Root cause
The "Restrict version tags" ruleset added in April 2026 protects
v*tags. GitHub treats the associated release as immutable once published — asset uploads return422 Cannot upload assets to an immutable release. This broke the release workflow starting with v0.30.3.Fix
Change the
create_releasestep to create the GitHub release as a draft (draft: true). Goreleaser finds the draft, uploads all assets, then publishes the release as its final step. Goreleaser already always uploads to a draft internally before publishing, so no goreleaser config changes are needed.🤖 Generated with Claude Code