[lewisjared]

Makes Renovate batch updates weekly and merge the low-risk groups by itself once CI passes. Dev dependencies (frontend and backend), GitHub Actions, Biome and lockfile maintenance now automerge. Frontend and backend runtime dependencies, climate-ref, the Python version, container images and every major open as their own PR and wait for a review.

• Updates open on Mondays only. Security fixes still open at any time.
• GitHub Actions are grouped. Before this, setup-uv, actions/cache and the Biome pin in ci.yml each opened a separate PR.
• @biomejs/biome in package.json and the Biome version in ci.yml share the "ci tooling" group, so they move together.
• platformAutomerge is off because main has no required status checks and repo auto-merge is disabled. Renovate merges itself after checking the branch status.
• Adds a ci-pass job that fails when any test, lint or build job fails or is cancelled. Once this merges, a separate ruleset will require only ci-pass, with no Renovate bypass, so nobody can merge red CI.

Validated with renovate-config-validator --strict.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Renovate’s configuration now sets revised schedules, concurrency and merge rules. It defines update groups for dependencies, development tooling, CI tooling and container images. A changelog entry describes weekly batching and merging after CI passes.

Changes: Renovate update policy

Layer / File(s)	Summary
Scheduling and merge policy renovate.json, changelog/160.trivial.md	The configuration sets a concurrency limit of 10, schedules PRs for Monday and changes automerge settings. Lockfile maintenance now runs on Monday and automerges. Vulnerability alerts can run at any time. The changelog describes weekly batching and merging after CI passes.
Dependency groups renovate.json	npm, pep621 and climate-ref updates use revised groups and automerge rules. Backend labels also match pyenv.
Tooling and major updates renovate.json	GitHub Actions and Biome updates use automerging groups. Docker updates use a container-images group. Major updates are ungrouped and cannot automerge.

Possibly related issues

• Renovate Dependency Dashboard #54: The issue tracks the Renovate Dependency Dashboard, which includes update types and settings changed by this PR.

Possibly related PRs

• Climate-REF/ref-app#146: Updates lockfiles and dependencies that this PR configures Renovate to schedule and group.
• Climate-REF/ref-app#145: Adds backend development tooling and GitHub Actions changes that this PR configures Renovate to group and automerge.
• Climate-REF/ref-app#156: Updates climate-ref, which this PR configures as a separate update group.

Priority: Pending latest changes

Change: Other

Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

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