Skip to content

Point Renovate and CodeRabbit at release/v5 - #264

Merged
Jake-Moore merged 1 commit into
release/v5from
fix/tooling-targets-release-v5
Sep 4, 2026
Merged

Point Renovate and CodeRabbit at release/v5#264
Jake-Moore merged 1 commit into
release/v5from
fix/tooling-targets-release-v5

Conversation

@Jake-Moore

@Jake-Moore Jake-Moore commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Every pull request in this repository targets release/v5, but GitHub's default branch is main.
Renovate and CodeRabbit both read the default branch and act on it unless told otherwise, so both
were pointed at a branch nobody develops on.

CodeRabbit had already stopped reviewing

It posts a comment rather than failing a check:

Auto reviews are disabled on base/target branches other than the default branch.

So pull requests merge unreviewed and nothing goes red. .coderabbit.yaml adds release/v5 to
reviews.auto_review.base_branches. The default branch stays covered automatically, so this adds
release/v5 rather than replacing anything.

Renovate was working by inheritance, not by configuration

Its pull requests have been landing on release/v5, but nothing in the repository says they should.
That behaviour is left over from when release/v5 was the default branch. The next time Renovate
resolves the default it opens against main instead, where dependency updates would sit unmerged
while release/v5 quietly goes stale. baseBranches writes the intent down.

When each takes effect

They differ, and the difference was measured on this pull request rather than assumed.

CodeRabbit reads .coderabbit.yaml from the branch. It picked this file up from the head of
this pull request and reviewed it, on a release/v5 base, before anything merged. Its own run
configuration reports Configuration used: Path: .coderabbit.yaml. So that half is live already.

Renovate reads its configuration from the default branch. baseBranches therefore does nothing
until it reaches main, and the sync from release/v5 is what activates it.

The alternative was changing GitHub's default branch to release/v5, which fixes both tools with
one setting. It was not taken because a setting that is invisible in the repository is what caused
this: reading the branch topology alone suggested release/v5 was a stale release line, when it is
where all the work happens.

Every pull request in this repository targets release/v5, but GitHub's
default branch is main. Both tools read the default branch and act on it
unless told otherwise, so both were pointed at a branch nobody develops
on.

CodeRabbit had already stopped reviewing. It posts a comment saying auto
reviews are disabled for base branches other than the default rather than
failing a check, so pull requests merge unreviewed and nothing goes red.

Renovate's pull requests have been landing on release/v5, but that is
inherited from when it was the default branch, not from anything written
down. The next time Renovate resolves the default it would open against
main instead, where the changes would sit unmerged.

Neither setting takes effect until it reaches the default branch, since
that is where both tools read their configuration.

Co-Authored-By: Claude Code <[email protected]>
@coderabbitai

coderabbitai Bot commented Sep 4, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 3eaf2523-0911-426f-9937-bc748d1e5663

📥 Commits

Reviewing files that changed from the base of the PR and between da05589 and 1f7e472.

📒 Files selected for processing (2)
  • .coderabbit.yaml
  • renovate.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The PR adds CodeRabbit and Renovate configuration. Both tools target the release/v5 branch. CodeRabbit automatic reviews are enabled.

Changes

Release branch automation

Layer / File(s) Summary
Branch-targeted automation configuration
.coderabbit.yaml, renovate.json
CodeRabbit enables automatic reviews for release/v5. Renovate also targets release/v5.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 1f7e4

This change directs CodeRabbit reviews and Renovate updates to release/v5 without changing the repository default branch. The configuration matches the intended branch targeting and is ready to merge.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: configuring Renovate and CodeRabbit to target release/v5.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/tooling-targets-release-v5

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.

@Jake-Moore
Jake-Moore merged commit dec856f into release/v5 Sep 4, 2026
2 checks passed
@Jake-Moore
Jake-Moore deleted the fix/tooling-targets-release-v5 branch September 4, 2026 11:28
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