Skip to content

Allow PyPI release retry after partial publish#174

Merged
zackees merged 1 commit intomainfrom
codex/fix-release-pypi-retry
Apr 22, 2026
Merged

Allow PyPI release retry after partial publish#174
zackees merged 1 commit intomainfrom
codex/fix-release-pypi-retry

Conversation

@zackees
Copy link
Copy Markdown
Member

@zackees zackees commented Apr 22, 2026

Summary

  • split release eligibility into separate build, GitHub release, and PyPI publish decisions
  • allow manual \workflow_dispatch\ to recover when the GitHub tag/release exists but PyPI is missing wheels
  • rebuild retry artifacts from the existing release tag and skip GitHub release creation in that path
  • set PyPI publish to skip existing files for partial-upload recovery
  • document the manual recovery path

This addresses the current v2.2.0 state: GitHub release/tag exists, PyPI latest is still 2.1.21, and PyPI has zero 2.2.0 files.

Verification

  • rebased branch on current \origin/main\ before and after edits
  • parsed .github/workflows/release-auto.yml\ with PyYAML and asserted job gates / skip-existing
  • syntax-checked the prepare shell script with Git Bash \�ash -n`n- simulated current release state: tag exists + PyPI file count 0 => build=true, publish_github=false, publish_pypi=true, release_ref=v2.2.0
  • \git diff --check`n- confirmed branch worktree has no untracked or uncommitted files

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 22, 2026

Warning

Rate limit exceeded

@zackees has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 33 minutes and 48 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 33 minutes and 48 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fe423c5b-968b-47e5-af05-31a2564d8eaa

📥 Commits

Reviewing files that changed from the base of the PR and between 0b25c83 and d9110d3.

📒 Files selected for processing (2)
  • .github/workflows/README.md
  • .github/workflows/release-auto.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/fix-release-pypi-retry

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@zackees zackees merged commit e2fae1e into main Apr 22, 2026
77 checks passed
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