Skip to content

Group more Renovate updates to cut PR count - #1345

Merged
danbarr merged 2 commits into
mainfrom
renovate/reconfigure
Nov 16, 2026
Merged

danbarr merged 2 commits into
mainfrom
renovate/reconfigure

Conversation

@danbarr

@danbarr danbarr commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

Description

Renovate opens a separate PR for each small npm update, which costs CI minutes and review time for no benefit. This morning's run opened #1334, #1335, and #1336 separately. This change groups more updates together and fixes two groups that were splitting by accident.

  • Non-major npm updates are now batched into one weekly "npm dependencies" PR that automerges once checks pass. Docusaurus stays in its own monorepo group so framework upgrades get a separate review. The linters and Playwright rules come later in the list, so they still take precedence.
  • Node.js majors now go out as one PR. Before this change, the Node 26 upgrade was split between Update Node.js to v26 #1340 (.nvmrc and engines) and Update dependency node to v26 #1342 (the setup-node version in CI). Merging only one of them would leave local and CI on different Node versions.
  • Playwright now uses the same 3-day release-age gate as GitHub Actions. Before, npm packages had to wait 3 days but the Docker image didn't, so the image moved ahead on its own (Update Playwright to v1.65.1 #1339). The Playwright rule also sets automerge: false explicitly, because otherwise @playwright/test would pick up automerge from the npm group, and Playwright bumps often change visual baselines.

Validated with renovate-config-validator --strict. Once this merges, Renovate should close or replace #1339, #1340, and #1342 on its next run.

Type of change

  • Build/tooling change (Renovate configuration)

Related issues/PRs

#1334, #1335, #1336, #1339, #1340, #1342

Submitter checklist

Content and formatting

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

Reviewer checklist

Content

  • I have reviewed the content for technical accuracy
  • I have reviewed the content for spelling, grammar, and style

🤖 Generated with Claude Code

Batch non-major npm updates into one automerged weekly PR, keeping
Docusaurus, linters, and Playwright in their own groups. Group Node.js
majors so .nvmrc, engines, and setup-node move together. Give the
Playwright group the same release-age gate as GitHub Actions so the
npm package and Docker image land in one PR, and keep Playwright out
of automerge since bumps often change visual baselines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs-website Ready Ready Preview Nov 16, 2026 3:56pm UTC

Request Review

Copilot AI balanced review requested due to automatic review settings November 16, 2026 15:45
@renovate

renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your Renovate settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:


Detected Package Files

  • .devcontainer/devcontainer.json (devcontainer)
  • .github/actions/setup/action.yaml (github-actions)
  • .github/workflows/_static-checks.yaml (github-actions)
  • .github/workflows/_visual-regression.yaml (github-actions)
  • .github/workflows/autogen-docs-notify.yml (github-actions)
  • .github/workflows/claude.yml (github-actions)
  • .github/workflows/dispatch-release-docs.yml (github-actions)
  • .github/workflows/enterprise-docs-notify.yml (github-actions)
  • .github/workflows/pr-screenshot-summary.yaml (github-actions)
  • .github/workflows/triage.yml (github-actions)
  • .github/workflows/update-visual-baselines.yaml (github-actions)
  • .github/workflows/upstream-release-docs.yml (github-actions)
  • .github/workflows/zizmor.yaml (github-actions)
  • package.json (npm)
  • plugins/mcp-metadata-plugin/package.json (npm)
  • .nvmrc (nvm)
  • docs/toolhive/guides-mcp/context7.mdx (regex)
  • docs/toolhive/guides-mcp/fetch.mdx (regex)
  • docs/toolhive/guides-mcp/filesystem.mdx (regex)
  • docs/toolhive/guides-mcp/github.mdx (regex)
  • docs/toolhive/guides-mcp/grafana.mdx (regex)
  • docs/toolhive/guides-mcp/k8s.mdx (regex)
  • docs/toolhive/guides-mcp/osv.mdx (regex)
  • docs/toolhive/guides-mcp/playwright.mdx (regex)
  • .github/upstream-projects.yaml (regex)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Pin github-action digests.
  • Append Signed-off-by: to signoff Git commits.
  • Disable semantic prefixes for commit messages and PR titles.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behavior in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run Renovate on following schedule: * 0-7 * * 1

What to Expect

With your current configuration, Renovate will create 9 Pull Requests:

Update anthropics/claude-code-action action to v1.0.276
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/github-actions
  • Merge into: main
  • Upgrade anthropics/claude-code-action to f3b070c88125d33dbae5653df5f143101d4ea9dc
Update linters
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/linters
  • Merge into: main
  • Upgrade @eslint-react/eslint-plugin to sha512-ObFCVyGqmYG/ojhVubMTqNg38GGifBP0eRauIylw15l7l7np7ilp9QI/VSBFDCCbXUEx1ArEmeRr4LGc7f+wgg==
  • Upgrade eslint to sha512-+5Wg4p+ze3sG1WErYgUO/3H1IQIfFBymVUA0Fo/XTeBOLS6UQIUekpSJ8sdRkn7O7wjh84b55w/roqavH2aScg==
  • Upgrade eslint-plugin-mdx to sha512-WR2W6Xj5kkZisjYy4ftJR/eXasgSUEEU980iEVN2DUJqNwBKCCKjizr8nSqB+aCblDNEkmx3HJFWCFnplyrwuA==
  • Upgrade lint-staged to sha512-3MXgVN7BERDR/6CXZs2fDHGc+r0+hlvGAa9wqMlVbIS6RVRuaPOnb5SnN6wMXulwfEy9DXVkMVUN/8cUlpPDnw==
Update mcr.microsoft.com/playwright Docker tag to v1.65.1
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/playwright
  • Merge into: main
  • Upgrade mcr.microsoft.com/playwright to sha256:1507cbfc550a63a6b7396791ca4f00df17beb56342d2447b3f106c306f525579
Update MCP usage guide Docker images
Update stacklok/toolhive to v0.66.0
  • Schedule: ["at any time"]
  • Branch name: renovate/stacklok-toolhive-0.x
  • Merge into: main
  • Upgrade stacklok/toolhive to v0.66.0
Update dependency typescript to v7
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==
Update Node.js to v26
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/major-node-major
  • Merge into: main
  • Upgrade node to 26
  • Upgrade node to 26.13.1
Update npm to v12
  • Schedule: ["* 0-7 * * 1"]
  • Branch name: renovate/npm-12.x
  • Merge into: main
  • Upgrade npm to sha512-KglgbZyacf7jH+FHuNRqVuCzQi8VhI2a7J87Ix43FsPTuZoGWmIXXGdZtBUOA79vwL+IJREqURVzupA7PsQTcA==
Lock file maintenance
  • Schedule: ["before 4am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 PR creation will be limited to maximum 4 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The linters rule leaves groupSlug unchanged, causing non-major linter updates to share the ordinary npm updates branch instead of remaining a separate group.

1 open issue
What changed in this PR

This PR adjusts Renovate policies for the ToolHive documentation website to reduce dependency-update PR volume and keep related runtime and testing updates together.

Changes:

  • Batches non-major npm updates into a weekly automerge group, excluding @docusaurus/*.
  • Groups Node.js major updates across local version declarations and CI setup.
  • Adds a three-day release-age policy to the Playwright group and explicitly disables its automerge.
File Description
renovate.json Updates npm and Node.js grouping rules and Playwright release-age and merge policies.

Review effort: Balanced

Comment thread renovate.json Resolved
An explicit groupSlug survives later rules that only change
groupName, which pulled linter updates onto the npm branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
@danbarr
danbarr merged commit c2a4f62 into main Nov 16, 2026
11 checks passed
@danbarr
danbarr deleted the renovate/reconfigure branch November 16, 2026 15:57

This branch was successfully deployed

1 active deployment
Preview — daded71e Deployed Nov 16, 2026 by vercel[bot]
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.

3 participants