ci: harden publish-pypi against accidental manual publishes (slice #50)#6
ci: harden publish-pypi against accidental manual publishes (slice #50)#6
Conversation
workflow_dispatch now defaults dry_run to "true" (was "false") and the publish job's if: predicate switches to a positive form so unexpected input values fail closed instead of publishing. Contract test locks both invariants in place. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning Rate limit exceeded
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 31 minutes and 9 seconds. ⌛ 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
RADE score diffCompared
Generated by RADE GitHub Action. |
Summary
Safety margin for a first-release repo wired to a trusted publisher.
Test plan
🤖 Generated with Claude Code