Repository navigation
ci(dev-lead): pin self-host caller to @dev-lead/next (canary) - #856
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
More reviews will be available in 42 minutes and 9 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE 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 |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-21T03:23:21Z. |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
|
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-21T04:27:06Z. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: 12e500c5e988e2200fe913713fa5ac302453e810
Review mode: triage-approved (single reviewer)
Summary
Two-line CI canary change: pins this repo's self-host dev-lead caller from the dev-lead/stable channel to dev-lead/next (both the reusable-workflow ref and the agent_ref input move together, as required). dev-lead/next resolves to ded84ce4 (main HEAD = v1.4.0), a valid commit. This is the documented Phase-2 candidate/green channel canary per versioning.md; rollback is a central tag move with no caller edit. dev-lead.yml is not a thin-caller stub, so editing it is permitted.
Linked issue analysis
No closing issue referenced (closingIssuesReferences empty). None required — this is an infrastructure canary rollout pinning the caller to the v1.4.0 release channel (release tracked under #781). Nothing to substantively address.
Findings
No issues found. The ref (uses:) and agent_ref input are updated in lockstep to dev-lead/next, avoiding channel skew. Reference is first-party (petry-projects/.github-private reusable workflow); the channel-tag pin (vs SHA) is the intended self-host pattern documented in the surrounding comment block to break the release circular dependency. No secrets, auth, crypto, or migrations touched; diff contains no credential material. MCP secret-scanning tool not exposed in this environment — gitleaks CI check passed.
CI status
All required checks green. Notable: Lint, shellcheck, bats, CodeQL (actions+python), SonarCloud (Quality Gate passed, 0 new issues), CodeRabbit SUCCESS, Secret scan (gitleaks) SUCCESS, AgentShield SUCCESS, Holdout Guard, unit-tests, Test Dev-Lead Agent suite all SUCCESS. Dependabot/npm/pnpm/govulncheck/cargo/pip audits SKIPPED (no matching ecosystems). Earlier advisory-bot rate-limit notices have since cleared (CodeRabbit + SonarCloud now report SUCCESS). mergeStateStatus BLOCKED only due to pending org-leads review (REVIEW_REQUIRED).
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.



Canary rollout of dev-lead v1.4.0 (the #781 release + accumulated main).
Pins this repo's self-host dev-lead caller to the new
dev-lead/nextchannel (candidate/green channel per versioning.md Phase 2).dev-lead/next→dev-lead/v1.4.0(= main HEADded84ce4).Staged ring plan (channels all cut at v1.4.0;
stableuntouched):next(this PR — canary)ring0ring1stable(unchanged, old version)Trigger-only stub change; rollback is a central tag move (no caller edit).
🤖 Generated with Claude Code