fix(ci): pypi-publish skip-existing=true so re-pushed tags don't go red#238
Merged
Conversation
publish-pypi.yml was failing with HTTP 400 'File already exists' when a v* tag got force-pushed (e.g. when fixing release.yml's Docker job for v0.5.2 — see #235). The publish step has nothing to do, but the action defaults to skip-existing=false, so the no-op surfaces as a failure. Set skip-existing=true: PyPI immutability means re-publish is a logical no-op anyway, and treating it as a hard error means every tag-fix dance leaves a red X behind that's actually a non-event. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Why
publish-pypi.yml currently fails with HTTP 400 `File already exists` whenever a v* tag gets force-pushed (which I did earlier today to fix release.yml's Docker job for v0.5.2 — see #235). The publish step has logically nothing to do (PyPI versions are immutable, so a re-push is a no-op), but the action defaults to `skip-existing: false`, so the no-op shows up as a red X on the publish-pypi workflow.
What
Set `skip-existing: true` on the `pypa/gh-action-pypi-publish` step. PyPI's immutability guarantee means we never overwrite an existing version anyway; this just turns "no-op publish" from a failure into a green skip.
Test plan
🤖 Generated with Claude Code