chore(renovate): stop proposing major bumps of indirect deps - #1173
Merged
Conversation
In Go a major version is part of the import path, so bumping one means editing import statements inside the module that requires it. For an indirect dependency that module is not this repo, and nothing here imports these packages, so the update is not actionable. The dashboard has been offering four of them every week: go.yaml.in/yaml/v2 -> v3 and gopkg.in/yaml.v2 -> v3 (both v3 modules are already in go.mod alongside their v2 counterparts, pulled in by different parents), plus go-github/v86 -> v90 and gitlab client-go -> v2. gomodTidy would revert any of them. Minor and patch updates for indirect deps still flow through the existing group, so transitive fixes are unaffected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
In Go a major version is part of the import path, so bumping one means editing
importstatements inside the module that requires it. For an indirect dependency that module is not this repo — and nothing inccatimports these packages — so the update can never be actioned here.gomodTidywould revert it anyway.The dependency dashboard (#10) has been offering four of them every week:
go.yaml.in/yaml/v2→v3.0.5go.yaml.in/yaml/v3 v3.0.5is already in go.mod — both are pulled in by different parentsgopkg.in/yaml.v2→v3.0.1gopkg.in/yaml.v3 v3.0.1is already theregithub.com/google/go-github/v86→v90gitlab.com/gitlab-org/api/client-go→v2Minor and patch updates for indirect deps still flow through the existing
go indirect dependenciesgroup, so transitive security fixes are unaffected. Validated withrenovate-config-validatorv44.🤖 Generated with Claude Code