ci(release): make the release workflow retry-safe#24
Merged
Conversation
A release can fail late (the 0.1.0 run created the tag + GitHub Release, then PyPI rejected the upload over a pending-publisher project-name mismatch). Recovering required deleting the tag by hand. Make every mutating step idempotent so a fixed re-run completes the publish: - validate: an existing tag is a notice, not a hard failure - tag creation is skipped when the tag already exists - PyPI publish uses skip-existing softprops/action-gh-release already updates an existing Release.
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 0.1.0 run created the tag
v0.1.0and the GitHub Release, then PyPI rejected the upload (400: Non-user identities cannot create new projects— a pending-publisher project-name mismatch, an account-side fix). Recovering would have needed manual tag deletion.Makes the mutating steps idempotent so a corrected re-run finishes the publish cleanly:
skip-existing: trueon the PyPI uploadsoftprops/action-gh-releasealready updates an existing Release. No version change.