Repository navigation
release: attach artifacts when the release already exists - #101
Open
rsantacroce wants to merge 1 commit into
Open
rsantacroce wants to merge 1 commit into
rsantacroce wants to merge 1 commit into
Conversation
Publishing v0.4.0 from the web UI pushed the tag, the tag push started this workflow, and 'gh release create' then failed with 'a release with the same tag name already exists' after both tarballs had built. The release went out with no binaries. If the release exists, upload the tarballs and SHA256SUMS to it and leave its notes alone.
This branch has not been deployed
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.
Publishing v0.4.0 from the GitHub UI pushed the tag, and that push started
release.yaml. Both tarballs built fine, butpublishthen rangh release create, which failed witha release with the same tag name already exists. The release went out with no binaries (run).Change: if the release already exists,
gh release upload --clobberattaches the tarballs andSHA256SUMSto it and leaves the maintainer's title and notes alone. Otherwise it creates the release as before, so thegit push origin vX.Y.Zpath is unchanged.v0.4.0 is already fixed by hand. The two tarballs that run built (commit
5f9ac48, the tag's commit, per each tarball'sRELEASEfile) were uploaded with aSHA256SUMSbuilt from the run's own.sha256files. A public download verifies withsha256sum -c.