ci(renovate): clarify Node docker digest commit text

[marcusrbrown]

No description provided.

[fro-bot]

Verdict: PASS

The new entry correctly narrows the commit message for Node.js Docker digest-only updates to produce clearer output like build(deps): bump Node.js to 20@abc1234 instead of the generic digest hash message Renovate would otherwise generate.

Correctness check:

• — consistent with the existing docker rule above it; no conflict since this rule is more specific (package name + update type filters apply first in Renovate's rule-merging).
• Regex /^((docker[.]io/library/)?node|library/node)$/ — covers the three canonical forms Renovate uses for the official Node image (node, docker.io/library/node, library/node). Correct.
• matchUpdateTypes: ['digest'] — scoped to digest-only bumps as intended. minor/patch version updates will keep the default commit message. Correct.
• commitMessageExtra: 'to {{currentValue}}@{{newDigestShort}}' — currentValue will be the tag (e.g. 20 or 20-alpine) and newDigestShort the short digest. Produces readable, unambiguous messages.
• Rule ordering: placed before the broader package-name block; Renovate merges all matching rules in order, so the semanticCommitType: 'build' from the datasource rule above still applies. No conflict.

Blocking issues

None

Non-blocking concerns

None

Missing tests

None — Renovate config changes are validated by the Renovate schema and integration; no unit tests apply here.

Risk assessment (LOW/MED/HIGH): LOW

This is a purely cosmetic change to commit message formatting for a specific, narrow match condition. It cannot break any workflow, dependency update, or runtime behavior.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/agent
Run ID	26553747174
Cache	hit
Session	ses_1934405e3ffefDSLq5jC1NzaEn

[fro-bot]

Verdict: PASS

The new packageRules entry correctly narrows the commit message for Node.js Docker digest-only updates to produce clearer output like build(deps): bump Node.js to 20@abc1234 instead of the generic digest hash message Renovate would otherwise generate.

Correctness check:

• matchDatasources: ['docker'] — consistent with the existing docker rule above it; no conflict since this rule is more specific (package name + update type filters apply first in Renovate's rule-merging).
• Regex /^((docker[.]io/library/)?node|library/node)$/ — covers the three canonical forms Renovate uses for the official Node image (node, docker.io/library/node, library/node). Correct.
• matchUpdateTypes: ['digest'] — scoped to digest-only bumps as intended. minor/patch version updates will keep the default commit message. Correct.
• commitMessageExtra: 'to {{currentValue}}@{{newDigestShort}}' — currentValue will be the tag (e.g. 20 or 20-alpine) and newDigestShort the short digest. Produces readable, unambiguous messages.
• Rule ordering: placed before the broader package-name block; Renovate merges all matching rules in order, so the semanticCommitType: 'build' from the datasource rule above still applies. No conflict.

Blocking issues

None

Non-blocking concerns

None

Missing tests

None — Renovate config changes are validated by the Renovate schema and integration; no unit tests apply here.

Risk assessment (LOW/MED/HIGH): LOW

This is a purely cosmetic change to commit message formatting for a specific, narrow match condition. It cannot break any workflow, dependency update, or runtime behavior.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/agent
Run ID	26553747174
Cache	hit
Session	ses_1934405e3ffefDSLq5jC1NzaEn