Repository navigation
ci: rely on bump to refuse an existing tag - #184
Merged
Merged
Conversation
release-actions v1.1.0 refuses an existing tag or release inside bump, before it writes a file. bump gets the App token, so it sees draft releases too.
mcanouil
marked this pull request as ready for review
October 16, 2026 13:39
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
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.
mcanouil/release-actionsv1.1.0 checks for an existing tag or release insidebump, before it writes a file.That makes the copied "Refuse an existing tag or release" step redundant, so this pull request removes it.
bumpnow gets the same App token that the step used.GitHub only shows a draft release to a token that can write, so the check still catches a draft.