🌱 ci: add dependabot config for nested Go modules - #2857
Conversation
Adds dependabot entries for the two nested go.mod files that were not previously tracked, which caused version drift and CI failures when the root module was bumped but the nested modules were not. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughDependabot now checks two Go module directories daily. Each configuration applies a 14-day cooldown and uses the ChangesDependabot Go Module Updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
go.modfiles that were not previously tracked:hack/ci/custom-linters/analyzers/testdata/hack/tools/test-profiling/Why
Dependabot was only watching the root
go.mod. The nested modules drifted, which causedunit-test-basicto fail when the root module was bumped but the nestedtestdatamodule was not (root module upgraded tov1.4.4, testdata still hadv1.4.3, and CI runs withGOPROXY=off).With this change, dependabot will open PRs for all three Go modules independently, keeping them in sync.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit