Skip to content

(chore): pin claude-pr-owner to v0.3.1#865

Merged
abnegate merged 2 commits intomainfrom
chore-bump-claude-pr-owner-0.3.0
Apr 23, 2026
Merged

(chore): pin claude-pr-owner to v0.3.1#865
abnegate merged 2 commits intomainfrom
chore-bump-claude-pr-owner-0.3.0

Conversation

@abnegate
Copy link
Copy Markdown
Member

Summary

Bumps the Claude PR orchestrator pin to v0.3.0, which fixes two issues that survived the v0.2.0 bump (#864):

  1. Classify-complexity still authenticated against the wrong endpoint. v0.2.0 tried to make the native `claude` CLI pick up `CLAUDE_CODE_OAUTH_TOKEN` by writing `~/.claude/.credentials.json`; the native binary installed by `install.sh` still exited with "Not logged in · Please run /login" (see run 24836809699, classification `'notloggedin·pleaser'`). v0.3.0 delegates classification to `anthropics/claude-code-base-action`, which uses the `@anthropic-ai/claude-agent-sdk` that handles the OAuth token correctly.

  2. Improvement looped on its own commits. Each `improvement` run that pushed a fix fired `pull_request.synchronize`, which re-ran improvement, committed again, and so on. v0.3.0's plan step now short-circuits `improvement` (pull_request) and `healing` (workflow_run) when the HEAD commit is authored by `claude-bot@users.noreply.github.com`. `bots` and `comments` are unaffected since they need external triggers.

Test plan

  • Push to a PR → `classify-complexity` logs a real classification (`simple`/`complex`), not empty/garbage.
  • Let improvement commit a fix → the subsequent synchronize run shows "HEAD commit ... authored by claude[bot]; skipping improvement to avoid self-trigger loop." and does not fan out.
  • An external review from a bot or `@claude` comment still fires `bots`/`comments` as before.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 23, 2026

Warning

Rate limit exceeded

@abnegate has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 13 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 20 minutes and 13 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: 91e07dcc-172d-4635-8b77-9547a51dc029

📥 Commits

Reviewing files that changed from the base of the PR and between fd591ea and d67c695.

📒 Files selected for processing (1)
  • .github/workflows/claude.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore-bump-claude-pr-owner-0.3.0

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.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 23, 2026

Greptile Summary

This chore PR bumps the pinned SHA of the abnegate/claude-pr-owner reusable workflow from the v0.2.0 commit to b8299b2a5f868e81dbb799a355b92a7b93b5d3dc (v0.3.1), picking up fixes for authentication against the wrong endpoint and an infinite improvement-loop on bot commits. Note that the PR description body references v0.3.0 while the title, code comment, and actual SHA correspond to v0.3.1 — a minor copy-paste inconsistency with no functional impact.

Confidence Score: 5/5

Safe to merge — single-line SHA pin bump with no logic changes in this repo.

The only changed line is a SHA reference update to a reusable workflow. No application code, tests, or configuration logic is affected. All findings are cosmetic (description body/title version mismatch) and do not warrant blocking merge.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/claude.yml Single-line bump of the reusable orchestrator workflow pin from v0.2.0 SHA to v0.3.1 SHA; no other changes.

Reviews (2): Last reviewed commit: "(chore): bump claude-pr-owner pin to v0...." | Re-trigger Greptile

@abnegate abnegate changed the title (chore): pin claude-pr-owner to v0.3.0 (chore): pin claude-pr-owner to v0.3.1 Apr 23, 2026
@abnegate abnegate merged commit d67c695 into main Apr 23, 2026
20 of 21 checks passed
@abnegate abnegate deleted the chore-bump-claude-pr-owner-0.3.0 branch April 23, 2026 13:29
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