ci: make PyPI workflow's release step idempotent#37
Merged
Conversation
The Publish to PyPI workflow creates the GitHub Release as its last step. When the release was already created by hand before pushing the tag, that step failed with "Release.tag_name already exists" and the whole run went red even though the PyPI upload (an earlier step) had succeeded. Skip release creation when the release already exists, so the run stays green regardless of whether the release was pre-created. Co-Authored-By: Claude Opus 4.8 <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
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.
Problem
The "Publish to PyPI" workflow creates the GitHub Release as its last step. When the release was already created by hand before the tag was pushed (as happened for v0.4.2), that step fails with
Release.tag_name already existsand the whole run goes red — even though the PyPI upload, an earlier step, had already succeeded.For v0.4.2 the package did publish to PyPI, npm, and Homebrew successfully; only this redundant step turned the PyPI run red.
Fix
Skip release creation when the release already exists, so the run stays green whether or not the release was pre-created:
The normal flow (push a tag, let the workflow create the release) is unchanged.
YAML validated locally.
🤖 Generated with Claude Code