fix: skip existing releases#17
Merged
Merged
Conversation
Open
bniladridas
commented
May 21, 2026
| GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| run: | | ||
| VERSION="${{ steps.version_check.outputs.new_version }}" | ||
| if gh release view "v${VERSION}" >/dev/null 2>&1; then |
Contributor
Author
There was a problem hiding this comment.
This guard keeps the release workflow idempotent. It matters after a release rerun or a main-history repair because the version can still look changed while the GitHub release/tag already exists; in that case the workflow should report the existing release and exit successfully instead of failing with a 422 from gh release create.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Verification