Update release workflow to support re-publishing existing releases#1234
Merged
joshmgross merged 3 commits intomainfrom Mar 30, 2026
Merged
Update release workflow to support re-publishing existing releases#1234joshmgross merged 3 commits intomainfrom
joshmgross merged 3 commits intomainfrom
Conversation
mscoutermarsh
approved these changes
Mar 30, 2026
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
This was referenced Mar 30, 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
2 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.
The new release workflow (#1232) is currently failing, this allows us to re-run it.
This will be useful for intermittent issues or misconfigurations to ensure we can always end up with a fully published release for every version. This is primarily relying on GoReleaser to be idempotent.
I'm intentionally not using the existing functionality of
workflow_dispatchto run against another branch - we always want to run the latest release workflow and configuration. This also avoids needing to allow thereleaseenvironment to run against arbitrary branches or tags, which could pose a security risk.