revert: remove ineffective mode replace from goreleaser#38
Merged
Conversation
mode: replace only controls release notes behavior, not the release itself. The actual cause of the immutable release 422 errors is that releases are being created via the GitHub UI before GoReleaser runs. Reverting to let GoReleaser handle release creation end-to-end. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the GoReleaser configuration to remove mode: replace from the release configuration, aligning the repo’s release automation with the clarified understanding that the observed “immutable release” failures are driven by how releases are created (published via GitHub UI) rather than by GoReleaser’s release-notes mode setting.
Changes:
- Remove
mode: replacefrom.goreleaser.yamlunder thereleasesection.
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
mode: replacefrom.goreleaser.yaml— it only controls release notes behavior, not how GoReleaser handles existing releasesContext
PR #37 added
mode: replacethinking it would fix the422 Cannot upload assets to an immutable releaseerror. It didn't — the v1.0.18 release failed identically. The actual root cause is that releases created via the GitHub UI are published (and therefore immutable) before GoReleaser runs. The fix is to push tags from CLI and let GoReleaser create the release itself.Test plan
🤖 Generated with Claude Code