build(deps): bump actions/checkout to v7.0.0 and claude-code-action to v1.0.169

[jrgilbertson]

Combines Dependabot PRs #26 and #25. Both touch the same two workflow files, so they're easier to review and land as one change.

Action	From	To	Type
actions/checkout	6.0.3	7.0.0	major
anthropics/claude-code-action	1.0.161	1.0.169	patch

Is the major bump safe?

Yes. The only breaking change in checkout v7.0.0 is #2454, which blocks checking out fork PRs under pull_request_target and workflow_run. Neither workflow uses those triggers:

• claude-code-review.yml runs on pull_request (opened, ready_for_review), already guarded by head.repo.full_name == github.repository.
• claude.yml runs on issue_comment, pull_request_review_comment, issues, and pull_request_review.

The rest of v7 is dependency bumps and an ESM module conversion.

Verification

• Both pinned SHAs dereferenced against their upstream tags and confirmed to match. claude-code-action's v1.0.169 is an annotated tag, so it required a second deref to reach commit 37b464c.
• Diff is exactly 4 lines, matching build(deps): bump actions/checkout from 6.0.3 to 7.0.0 #26 and build(deps): bump anthropics/claude-code-action from 1.0.161 to 1.0.169 #25 combined.
• git diff --check clean; both workflow files parse as YAML with their jobs intact.

Closes #26. Closes #25.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RZQncw11MKALwEnvymwxHb

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 51fd07a1-b310-461a-89c1-29914803bf8c

📥 Commits

Reviewing files that changed from the base of the PR and between 6d74f1d and d3e33ed.

📒 Files selected for processing (2)

• .github/workflows/claude-code-review.yml
• .github/workflows/claude.yml

---

_{Comment @coderabbitai help to get the list of available commands.}