Skip to content

chore(CI): use fix(deps) commit type for gomod updates and separate custom.regex group #3533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
apeabody wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(CI): use fix(deps) commit type for gomod updates and separate custom.regex group #3533

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .github/renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,7 @@
"matchManagers": [
"gomod"
],
"semanticCommitType": "fix",

@gemini-code-assist gemini-code-assist Bot Nov 12, 2026

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.

medium

Setting "semanticCommitType": "fix" on the general gomod manager rule will also cascade to the subsequent golang-version rule (lines 83-92), which matches the gomod manager and golang-version datasource.

Since Go toolchain/version updates are typically considered maintenance or toolchain updates (chore) rather than bug fixes (fix), they might trigger unnecessary production releases if they use semantic-release or similar tools.

Consider explicitly overriding "semanticCommitType": "chore" in the golang-version rule to keep Go version updates as chore.

@apeabody apeabody Nov 12, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Intentionally keeping golang-version updates as fix(deps):. Both go / toolchain directive updates and module require updates touch the same go.mod file and are grouped together in the {{packageFileDir}} deps PR, and bumping the go directive in go.mod updates the published module metadata and the Go toolchain (go-version-file) used to build released binaries.

"constraintsFiltering": "strict",
"postUpdateOptions": [
"gomodTidy",
Expand Down Expand Up @@ -107,9 +108,10 @@
"matchManagers": [
"custom.regex"
],
"semanticCommitType": "chore",
"additionalBranchPrefix": "",
"groupName": "{{#if packageFileDir}}{{{packageFileDir}}} deps{{else}}root deps{{/if}}",
"groupSlug": "{{#if packageFileDir}}{{{replace '/' '-' packageFileDir}}}-deps{{else}}root-deps{{/if}}"
"groupName": "{{#if packageFileDir}}{{{packageFileDir}}} tooling deps{{else}}root tooling deps{{/if}}",
"groupSlug": "{{#if packageFileDir}}{{{replace '/' '-' packageFileDir}}}-tooling-deps{{else}}root-tooling-deps{{/if}}"
},
{
"matchManagers": [
Expand Down
Loading