ci: fix release workflow to handle existing releases#8
Merged
Conversation
Split release creation and asset upload into separate steps. Create step skips gracefully if release already exists, upload step uses --clobber to overwrite existing assets.
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
|| true)--clobberto overwrite existing assetsFixes the failure when re-running the workflow for an existing tag.
After merging
Delete and re-push the
v1.0.0tag to re-trigger the workflow:git push origin :refs/tags/v1.0.0 git tag -fa v1.0.0 -m "v1.0.0" git push origin v1.0.0Test plan