fix(release): replace existing assets so GoReleaser can finish - #19
Merged
Merged
Conversation
The v0.4.0 Release job built and created the GitHub release, then 422'd uploading assets that were already there. GoReleaser aborted before pushing the Homebrew cask. Allow replacing existing artifacts so a re-release can complete and publish the tap.
This was referenced Aug 28, 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
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.
Summary
422 already_existson every upload).release.replace_existing_artifacts: trueso a re-run replaces those assets and can finish (including the cask publish).Test plan
Casks/powerctl.rbto the tapCasks/powerctl.rbat 0.4.0