Skip to content

Commit c6bfde1

Browse files
ci(renovate): force chore(deps) on direct Go modules via user packageRule
The top-level semanticCommitType=chore did not actually take effect for direct dependencies. config:recommended extends :semanticPrefixFixDepsChoreOthers, whose packageRule re-sets semanticCommitType=fix for depTypes [dependencies, require]. Renovate packageRules override top-level config, and the gomod manager assigns depType "require" to direct deps — so direct-dep PRs (the dominant type) still resolved to fix(deps) and were auto-labeled kind/bug, the exact pollution this PR set out to remove. Add a user packageRule (evaluated last, so it wins over the preset rule) that forces semanticCommitType=chore / scope=deps for the gomod manager. The top-level keys are now redundant but kept for readability. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 71690d1 commit c6bfde1

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

‎.github/renovate.json‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,12 @@
1818
"labels": ["automated", "security"]
1919
},
2020
"packageRules": [
21+
{
22+
"description": "Force chore(deps) for all Go module bumps. config:recommended pulls in :semanticPrefixFixDepsChoreOthers, whose packageRule re-sets semanticCommitType=fix for direct deps (depType require), overriding the top-level chore. packageRules override top-level config, so a user rule evaluated last is required to win it back; without this, direct-dep PRs land as fix(deps) and get auto-labeled kind/bug.",
23+
"matchManagers": ["gomod"],
24+
"semanticCommitType": "chore",
25+
"semanticCommitScope": "deps"
26+
},
2127
{
2228
"description": "Bump indirect Go modules too. Transitive deps such as golang.org/x/crypto, golang.org/x/net and golang.org/x/sys carry OSV advisories that drive the OpenSSF Scorecard Vulnerabilities check to 0, but Renovate skips indirect gomod deps by default so they never get a PR. Grouped into one rolling PR to keep volume sane; security fixes are still split out by vulnerabilityAlerts above. Placed before the kubernetes rule on purpose: an indirect k8s.io/** dep matches both, and Renovate applies last-match-wins, so the later kubernetes rule keeps it in the kubernetes lockstep group.",
2329
"matchManagers": ["gomod"],

0 commit comments

Comments
 (0)