Repository navigation
ci: release workflow leaves an existing release alone - #24
Merged
Merged
Conversation
gh release create pushes the tag itself, so a release made by hand triggered this workflow, which tried to create it again and failed with 'already exists' — v6.0.2, v6.1.0 and v6.2.0 went red over releases that are fine. It now skips the step when the release exists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The
releaseruns for v6.0.2, v6.1.0 and v6.2.0 failed (e.g. 40380876693):HTTP 422 … Release.tag_name already exists.Cause
Those releases were created by hand with
gh release create, which also pushes the tag. The tag push triggered this workflow, which tried to create the same release again. The releases themselves are fine — same title (the tag) and notes (the CHANGELOG section) the workflow would have written; only the duplicate step failed.Fix
"Publish it" skips when the release already exists (as the plugin's workflow does), so a hand-made release no longer turns the run red. The normal path — push a tag, the workflow creates the release — is unchanged.
The three red runs can't be turned green by re-running: a re-run uses the workflow file at the tagged commit. From here on, releases of this repository are published by pushing the tag.
🤖 Generated with Claude Code