Inconsistent commit message rendering for single-item group PRs (group size = 1)

[peiyanlu]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.209.0

Please tell us more about your question or problem

When using grouped updates (e.g. group:allNonMajor or custom groupName rules), Renovate may still render group-level commit message templates (including commitMessageExtra and/or group version aggregation) even when the resulting PR contains only a single dependency update.

This leads to a semantic mismatch between:

• PR type: effectively a single-dependency update
• PR classification: group update
• commit message output: group-style message with aggregated version

When only one dependency is eligible for update, Renovate generates a grouped PR such as:

Update all non-major dependencies to ^42.3.2

Expected behavior

When a grouped PR resolves to exactly one dependency update, Renovate could optionally:

Option A — fallback to single dependency template

Treat the PR as a non-group commit message context:

Update dependency @swc/core to ^42.3.2

Option B — suppress group-level message augmentation

Keep group PR structure but avoid:

• aggregated version in title
• commitMessageExtra injection

Result:

Update all non-major dependencies

Configuration

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "schedule:weekly",
    "group:allNonMajor"
  ],
  "automerge": true,
  "automergeType": "pr",
  "automergeStrategy": "rebase",
  "timezone": "Asia/Shanghai",
  "labels": ["dependencies"],
  "prConcurrentLimit": 0,
  "prHourlyLimit": 0,
  "rangeStrategy": "bump",
  "packageRules": [
    {
      "matchPackageNames": ["@types/node", "typescript", "vite", "node"],
      "enabled": false
    }
  ]
}

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[jamietanna]

We'd recently change this behaviour with groupSingleUpdates=true - it's possible to continue the previous behaviour by setting that to false

[peiyanlu]

Thanks a lot for the quick reply and the config suggestion 🙌

Just tested it and it works as expected now

Really appreciate the help!

[felipecrs]

I agree this is weird.

Suppressing the version in such case would probably make the most sense:

- Update all non-major dependencies to ^42.3.2
+ Update all non-major dependencies

On the other hand, Renovate doesn't recommend grouping all updates like that. Recommended groups are limited to similar dependencies. Like:

Update docusaurus monorepo dependencies to ^42.3.2

Even if all docusaurus components were already up to date and a single one was pending, which would still make sense.

[felipecrs]

Addressed this specific issue here:

• fix: omit version from pr title if group has a single update #43970