Skip to content

chore(renovate): widen sane automerges - #401

Merged
Zeryther merged 1 commit into
mainfrom
claude/renovate-automerge-config-31aa91
Jul 24, 2026
Merged

chore(renovate): widen sane automerges#401
Zeryther merged 1 commit into
mainfrom
claude/renovate-automerge-config-31aa91

Conversation

@Zeryther

Copy link
Copy Markdown
Member

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, and internalChecksFilter: strict).

Now automerges (previously manual)

Change Rationale
lockFileMaintenance → automerge Re-resolves the lockfile within existing ranges; nothing lands unless CI stays green.
pin / pinDigest updates Never change the resolved version — only make an existing version explicit. Also clears the stuck #337 "pin dependencies" PR.
Runtime-dependency patch Semver bugfixes. The 3-day age guard means a same-day bad release can't slip in. minor stays manual, major stays dashboard-gated.
patch inside the manually-reviewed groups (eslint, prettier, vitest, effect, react, radix, storybook, tailwind, rsbuild) The documented cross-version incompatibilities live at minor/major, not patch. Each group's automerge: false is scoped to ["minor", "major"], so patches flow through while minor/major stay grouped and manual.

Deliberately left manual

  • All major updates — still require dependency-dashboard approval.
  • Runtime minor — ships to users.
  • pnpm catalog (pnpm-workspace.yaml) — its one entry is typescript, which drives the whole monorepo's type surface.
  • The ESLint v10 hold — untouched.

Behavior note

Grouped ecosystems (radix, storybook, effect, vitest…) are monorepos already grouped by the group:monorepos preset, 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

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]>
@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sdk-harmony Ready Ready Preview, Comment Jul 24, 2026 4:10pm

Request Review

@changeset-bot

changeset-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 38c8bdf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@Zeryther, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 51fcd83c-1037-4831-b500-b9be78d681e4

📥 Commits

Reviewing files that changed from the base of the PR and between 5be3214 and 38c8bdf.

📒 Files selected for processing (1)
  • renovate.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/renovate-automerge-config-31aa91

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.

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@Zeryther, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 51fcd83c-1037-4831-b500-b9be78d681e4

📥 Commits

Reviewing files that changed from the base of the PR and between 5be3214 and 38c8bdf.

📒 Files selected for processing (1)
  • renovate.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/renovate-automerge-config-31aa91

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.

@Zeryther
Zeryther merged commit 056ecbc into main Jul 24, 2026
13 checks passed
@Zeryther
Zeryther deleted the claude/renovate-automerge-config-31aa91 branch July 24, 2026 16:13
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