chore(renovate): widen sane automerges - #401
Conversation
Increase the number of low-risk updates Renovate can automerge while keeping the guardrails (4 CI checks, 3-day minimumReleaseAge, strict internal checks) intact: - Automerge lockFileMaintenance (re-resolves lockfile within ranges). - Automerge pin and pinDigest updates (resolved version never changes). - Automerge runtime dependency patch updates (semver-safe bugfixes); minor stays manual, major stays dashboard-gated. - Automerge patch releases inside the manually-reviewed tool groups (eslint, prettier, vitest, effect, react, radix, storybook, tailwind, rsbuild); minor/major stay grouped and manual, where the documented cross-version incompatibilities actually live. Majors, runtime minors, and the pnpm catalog (typescript) remain manual. Co-Authored-By: Claude Opus 4.8 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
Warning Review limit reached
Next review available in: 37 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Warning Review limit reached
Next review available in: 37 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
What & why
Increase the number of low-risk dependency updates Renovate can automerge, so fewer safe PRs sit waiting on a manual click — while keeping every existing guardrail (the 4 CI checks,
minimumReleaseAge: 3 days, andinternalChecksFilter: strict).Now automerges (previously manual)
lockFileMaintenance→ automergepin/pinDigestupdatesminorstays manual,majorstays dashboard-gated.automerge: falseis scoped to["minor", "major"], so patches flow through while minor/major stay grouped and manual.Deliberately left manual
pnpm-workspace.yaml) — its one entry istypescript, which drives the whole monorepo's type surface.Behavior note
Grouped ecosystems (radix, storybook, effect, vitest…) are monorepos already grouped by the
group:monorepospreset, so patches stay grouped. A pure-patch group PR automerges; a PR mixing a patch with a minor/major won't, because Renovate only automerges a PR when every update in it is automergeable — the safe outcome.Config passes
renovate-config-validator.🤖 Generated with Claude Code