Skip to content

Fix: skip-existing on PyPI publish (recurring 400 File already exists)#18

Open
NameetP wants to merge 1 commit into
mainfrom
fix/pypi-skip-existing-clean
Open

Fix: skip-existing on PyPI publish (recurring 400 File already exists)#18
NameetP wants to merge 1 commit into
mainfrom
fix/pypi-skip-existing-clean

Conversation

@NameetP

@NameetP NameetP commented Jun 29, 2026

Copy link
Copy Markdown
Owner

Problem

The "Publish to PyPI" workflow fails with 400 File already exists when it re-runs on a package version already published (seen 2026-06-15, 2026-06-16).

Fix

Adds skip-existing: true to the pypa/gh-action-pypi-publish step so re-runs become a no-op instead of a hard 400. Workflow-only change.

Replaces #17, which was inadvertently branched off a local main carrying embargoed pre-filing commits. This branch is cut cleanly from origin/main — diff is the single workflow line.

🤖 Generated with Claude Code

The Publish-to-PyPI workflow errors with '400 File already exists' when it
re-runs on an already-published version (seen 2026-06-15, 2026-06-16). Adding
skip-existing makes re-runs idempotent.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant