Repository navigation
ci(release): skip creating the release when one already exists - #53
Merged
Merged
Conversation
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.
Why
Releases are written by hand and published as soon as the tag is pushed. The workflow's publish step then ran
gh release createagainst a tag that already had a release and failed withRelease.tag_name already exists. That left thev3andv4tag runs red even though their tests and typecheck passed.Change
gh release viewfirst. If a release for the tag exists, it logs that and leaves the release untouched. Otherwise it creates one with--generate-notes, as before.Not changed
A release published by hand still goes out before the tag's test run finishes. For v4 the tests passed about 45 seconds after publishing. To keep the "tag passed CI before release" guarantee, publish after the run is green, or save the hand-written release as a draft and publish it once the run passes.
Not run on a real tag yet. It will first run on
v5.🤖 Generated with Claude Code