Ensure script/release.sh is idempotent#1235
Merged
joshmgross merged 3 commits intomainfrom Mar 30, 2026
Merged
Conversation
dgraham
approved these changes
Mar 30, 2026
mscoutermarsh
approved these changes
Mar 30, 2026
GoReleaser doesn't allow skipping just the GitHub publish step, so this allows the rest of the release to be idempotent.
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 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.

The assumption in #1234 that GoReleaser was idempotent was not correct, the workflow failed when attempting to republish existing assets to the GitHub Release -
https://github.com/planetscale/cli/actions/runs/23766950223/job/69248755043
GoReleaser does have aWe can't avoidreplace_existing_artifactsoption, but I do not want to replace existing published releases.replace_existing_artifactsas far as I can tell - 844cf16This adds some level of idempotency to
script/release.shby checking if a version already exists for each publish target.