chore(deps): Split root into its own Dependabot gomod entry#124
Merged
Conversation
Sharing one multi-directory go-dependencies group with the AWS/Google submodules made Dependabot normalize root's go directive to the group maximum (1.25.0 -> 1.25.8 in #123) even with no root dependency change. Isolating root in its own entry keeps its go directive driven solely by root's own closure (go 1.24 via wfs), while still auto-updating its direct deps.
mojatter
force-pushed
the
chore/dependabot-drop-root-gomod
branch
from
ef1dbaa to
fe2bdfb
Compare
mojatter
changed the title
This was referenced May 31, 2026
mojatter
added a commit
that referenced
this pull request
May 31, 2026
The root (/) entry sat on go.work, so Dependabot ran workspace-wide and rewrote root's go directive even with no root dependency change. Dropping it keeps root's go.mod untouched; this supersedes the #124 split, which still produced a root-touching PR. Add /server so its own deps are tracked.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The root module (
/) only depends directly ongithub.com/mojatter/wfs(bumped manually via intra-repo dep PRs) andgithub.com/stretchr/testify. Its dependency closure needs at mostgo 1.24(via wfs), so root never requires a recent Go toolchain on its own.The problem: root shared a single multi-directory
go-dependenciesgroup with the AWS/Google submodules. Dependabot normalized that group'sgodirective to the group maximum and wrote it into every directory — including root — even when no root dependency changed. In #123 root'sgo.moddiff was only thegoline:go 1.25.0→go 1.25.8, borrowed entirely from the aws-sdk / google-api submodules.What
Move root (
/) into its owngomodupdate entry, separate from the submodules. Root'sgodirective is then driven solely by root's own dependency closure (go 1.24→1.25.0) and is no longer coupled to the submodules'1.25.8.Unlike simply dropping root from Dependabot, this keeps root's direct dependencies (e.g.
testify) under automated updates.Notes
go 1.25.8,go.work(which must be ≥ every member) stays ≥ root's1.25.0.go-directive normalization is inferred from the chore(deps): bump the go-dependencies group across 3 directories with 4 updates #123 behavior rather than documented, so the first Dependabot run after this lands is worth a glance to confirm root'sgodirective stays put.