ci: skip already-published versions when publishing to PyPI#81
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The publish job failed with a 400 "File already exists" when the release workflow re-ran for an already-published version (e.g. a double-trigger across consecutive merges). Set skip-existing so re-runs skip the upload instead of failing the release. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #81 +/- ##
=======================================
Coverage 93.43% 93.43%
=======================================
Files 10 10
Lines 1857 1857
Branches 239 239
=======================================
Hits 1735 1735
Misses 84 84
Partials 38 38 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3f6a862 to
a4f4710
Compare
Who's affected
Maintainers cutting releases — the release workflow's
publishjob currently goes red when PyPI already has the version being published.What changed
The v1.10.0 release succeeded (tag, GitHub release, and PyPI artifacts all published), but the
publishjob reported failure with400 File already existsbecausepypa/gh-action-pypi-publishran for an already-published version (a double-trigger across consecutive merges). Addingskip-existing: truemakes the upload idempotent: if the version is already on PyPI, it skips instead of failing the release.Agent context
.github/workflows/release.ymlpublish step; no code, no release-please config changes.