renovate-config

Shared Renovate configuration presets for our projects.

---

How to use

In your repository config (renovate.json, or renovate.json5), you add this preset in the extends section like so:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "github>boost/renovate-config:default.json5#v0.1.0"  // < reference our shared config like this
  ],
  "baseBranchPatterns": ["/^batched-updates.*/"],
  "packageRules": [
    // add your repo-specific rules
  ]
}

NOTES

• Even though it is in the base config already, you'll want to add "baseBranchPatterns": ["/^batched-updates.*/"] in your config too, or you'll get a warning. Think it's a bug.
• You'll want all your extra rules to include the filter "matchBaseBranch": "/^batched-updates.*/"

Our approach

• Renovate creates PRs targeting branches matching batched-updates...
  (e.g. batched-updates, batched-updates-april-2026)

  • Work happens across multiple PRs, but is tested and deployed as a single batch

• All PRs require manual approval via the dashboard

  • This gives us full control over what gets created and when

• Updates are grouped where it makes sense

  • Reduces CI/pipeline noise
  • Makes reviews more manageable

• We avoid adding exclusions where possible

  • The goal is to update everything regularly
  • If something is painful, we fix the root cause rather than muting it

  💡 Tip: You can approve a PR and then close it to move it into the Blocked section of the dashboard.
  This is useful for large upgrades (e.g. framework changes) that need a separate plan.

---

Suggested workflow

1. Create a new batching branch (e.g. batched-updates-april-2026)

2. Push the branch

3. Open the Renovate dashboard
   (Issues → Renovate Dashboard)

4. Approve PR creation for:

   • Indirect dependencies
   • Minor & patch updates
   • Major updates (review carefully and check changelogs)

5. As PRs are created:

   • Review them
   • Ensure CI passes
   • Merge into the batched-updates... branch

6. Once ready, open a PR from batched-updates... → main

   • Include links to the individual PRs in the description
   • Check for deprecation warnings and make sure they're fixed (makes major updates later less breaky)

7. Review, test, and deploy the batch

---

Gotchas

• Nothing happens until you approve it
  Renovate won’t create PRs automatically. If you’re not seeing updates, check the dashboard.

• Branch name must match the pattern
  If there isn't an open branch called batched-updates..., the dashboard will be empty.

• Closing a PR doesn’t mean it’s gone forever
  Closed PRs move to the Blocked section and won’t be recreated unless you take action.

• Config in the batched-updates branch overrides config in main
  We use useBaseBranchConfig=merge. This means you can test renovate config changes before merging into main.

---