chore: add --clobber to gh release upload for .sig files - #106
Merged
Conversation
When the release workflow is retried, the .sig files already exist on the release, causing `gh release upload` to fail. The --clobber flag allows overwriting existing assets. Signed-off-by: Claude <noreply@anthropic.com> https://claude.ai/code/session_01YSiCTG5xhX1fqNV4Vee5PX Signed-off-by: Claude <noreply@anthropic.com>
its-mash
changed the title
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.
When the release workflow is retried, the .sig files already exist on the
release, causing
gh release uploadto fail. The --clobber flag allowsoverwriting existing assets.
Signed-off-by: Claude noreply@anthropic.com
https://claude.ai/code/session_01YSiCTG5xhX1fqNV4Vee5PX
Signed-off-by: Claude noreply@anthropic.com