ci: migrate pr-auto-review → @pr-auto-review/stable (canary) - #315
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
There was a problem hiding this comment.
Pull request overview
Migrates the PR auto-review workflow caller stub to reference the org reusable workflow via the @pr-auto-review/stable first-party channel, aligning with the new canary/ring rollout model while keeping behavior pinned to the same underlying code.
Changes:
- Re-pins the reusable workflow reference from a commit SHA (
# v2) to the@pr-auto-review/stablechannel ref. - Adds an inline Sonar suppression note indicating this is an intentional first-party channel reference.



Migrate pr-auto-review off the frozen
@v2tag onto its canary ring channel. pr-auto-review is now under the canary/ring model (petry-projects/.github#669): v1.0.0 was cut at @v2's exact commit, so this is a zero-behavior-change repin — same code, now staged/gated for future changes instead of big-bang @v2 moves.