Skip to content

ci(publish): make the PyPI upload idempotent so a Release cannot go red over a duplicate #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vdavez merged 1 commit into from
Aug 4, 2026
+5 −1
Merged

ci(publish): make the PyPI upload idempotent so a Release cannot go red over a duplicate #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,4 +26,8 @@ jobs:
- name: Publish to PyPI
env:
UV_PUBLISH_TOKEN: ${{ secrets.TANGO_PYPI_TOKEN }}
run: uv publish
# --check-url makes the upload idempotent: uv queries the index first and skips
# files already present instead of failing the run. Without it, any version that
# reached PyPI by another route — a manual `uv publish`, a re-run of this
# workflow — makes the GitHub Release that follows it go red for no real reason.
run: uv publish --check-url https://pypi.org/simple/
Loading