Skip to content

ci(dev-lead): pin self-host caller to @dev-lead/next (canary) - #856

Merged
don-petry merged 2 commits into
mainfrom
claude/dev-lead-canary-next-ring
Jun 21, 2026
Merged

don-petry merged 2 commits into
mainfrom
claude/dev-lead-canary-next-ring

Conversation

@don-petry

Copy link
Copy Markdown
Collaborator

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/next channel (candidate/green channel per versioning.md Phase 2). dev-lead/next → dev-lead/v1.4.0 (= main HEAD ded84ce4).

Staged ring plan (channels all cut at v1.4.0; stable untouched):

  • .github-private → next (this PR — canary)
  • petry-projects/.github → ring0
  • TalkTerm → ring1
  • everyone else → stable (unchanged, old version)

Trigger-only stub change; rollback is a central tag move (no caller edit).

🤖 Generated with Claude Code

@don-petry
don-petry requested a review from a team as a code owner June 21, 2026 02:22
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai

coderabbitai Bot commented Jun 21, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a59e9fa4-146a-426c-91c5-3dc2584294e6

📥 Commits

Reviewing files that changed from the base of the PR and between f706d66 and 12e500c.

📒 Files selected for processing (1)
  • .github/workflows/dev-lead.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/dev-lead-canary-next-ring

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.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry
don-petry enabled auto-merge (squash) June 21, 2026 02:22
@donpetry-bot

Copy link
Copy Markdown
Contributor

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.

@don-petry
don-petry disabled auto-merge June 21, 2026 03:24
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry
don-petry enabled auto-merge (squash) June 21, 2026 03:24
@sonarqubecloud

Copy link
Copy Markdown

@donpetry-bot

Copy link
Copy Markdown
Contributor

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.

@don-petry
don-petry disabled auto-merge June 21, 2026 03:27
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 0
Files changed: (none required)
Skipped (informational): 1 — Quality Gate passed report, no code issues found
```

@don-petry
don-petry enabled auto-merge (squash) June 21, 2026 03:27

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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.

2 participants