[setchy]

Summary

Groups every Node.js-related update into a single PR:

• Runtime — Docker node images, engines.node, devEngines.runtime, .nvmrc, .node-version, .tool-versions/mise, and volta (all docker or node-version datasources)
• Types — @types/node (npm datasource)

Two rules share groupName: "node", so Renovate merges matches from different datasources into one branch/PR.

{
  "description": "Group Node.js runtime updates across Docker images, nvm, nodenv, asdf, mise, engines, and devEngines",
  "matchDatasources": ["docker", "node-version"],
  "matchPackageNames": ["/(?:^|/)node$/"],
  "groupName": "node",
  "commitMessageTopic": "Node.js"
},
{
  "description": "Group @types/node updates with the Node.js runtime",
  "matchDatasources": ["npm"],
  "matchPackageNames": ["@types/node"],
  "groupName": "node",
  "commitMessageTopic": "Node.js"
}

The Docker matcher uses upstream's regex ((?:^|/)node$) without its Kubernetes/helper-image exclusions, since the org does not use kindest/node or calico/node.

Why not just extend group:nodeJs? Upstream's preset only sets commitMessageTopic — it has no groupName, so it renames the commit but does not group branches (see Renovate's lib/config/presets/internal/group.preset.ts).

Scope notes:

• Applies org-wide through the shared preset.
• engines.node keeps rangeStrategy: auto, so supported ranges are not pinned.
• @types/node major policy stays per repository; grouping only merges the resulting PRs.
• No automerge.

Verification

• default.json parses as valid JSON
• The renovate-config-validator workflow runs on this PR
• Consumers pick it up on their next Renovate run