Skip to content

Let a release retry overwrite the assets it already uploaded #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adhikjoshi merged 1 commit into from
Sep 9, 2026
Merged

Let a release retry overwrite the assets it already uploaded #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .goreleaser.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,10 +38,15 @@ checksum:
name_template: "checksums.txt"

release:
# Re-running a release must be safe. The default `keep-existing` leaves a
# half-published release from a failed run in place, so the retry cannot
# correct it; `replace` makes the tag's assets match whatever this run built.
# Re-running a release must be safe.
#
# `mode` governs the release NOTES only — it does nothing about artifacts, and
# the v0.2.0 retry died proving it: every upload came back
# `422 already_exists` against the assets the first, half-failed run had
# already attached. replace_existing_artifacts is the half that actually
# overwrites them.
mode: replace
replace_existing_artifacts: true

snapshot:
version_template: "{{ incpatch .Version }}-next"
Expand Down
Loading