deps: group k8s.io minor updates in dependabot config - #2512
Merged
Conversation
Quang Nguyen (nddq)
requested review from
Mathew Merrick (matmerr) and
Vipul Singh (vipul-21)
July 10, 2026 20:13
7 tasks
The k8s dependabot group only covers patch updates, so k8s release trains (v0.35 -> v0.36 across k8s.io/api, apimachinery, client-go, kubectl, metrics, ...) arrive as individual PRs. Those modules version in lockstep — a lone bump is unresolvable (k8s.io/metrics v0.36 requires k8s.io/api v0.36, which drops packages the still-pinned k8s.io/kubectl v0.35 imports), and the sigs.k8s.io/controller-runtime minor that pairs with each train fails the same way. Extend the group to minor updates so the whole lockstep set ships as one PR. Majors stay excluded; k8s.io core modules are perpetually v0.x, so the release train is always a minor. Signed-off-by: Quang Nguyen <nguyenquang@microsoft.com>
Quang Nguyen (nddq)
force-pushed
the
fix/dependabot-k8s-group-minor
branch
from
July 13, 2026 14:29
86e384a to
709b892
Compare
Retina Code Coverage ReportTotal coverage no change |
Mereta (mereta)
approved these changes
Jul 13, 2026
Laksh (lakshk98)
pushed a commit
to lakshk98/retina
that referenced
this pull request
Aug 4, 2026
# Description The `k8s` dependabot group only covers `patch` updates, so k8s release trains (`v0.35` → `v0.36` across `k8s.io/api`, `apimachinery`, `client-go`, `kubectl`, `metrics`, …) arrive as individual PRs. Those modules version in lockstep, so a lone bump is unresolvable — microsoft#2329 has been failing dependency resolution for weeks: ``` k8s.io/metrics | dependency_file_not_resolvable | "go: ...k8s.io/kubectl/pkg/scheme imports k8s.io/api/scheduling/v1alpha1: module k8s.io/api@latest found (v0.36.2), but does not contain package k8s.io/api/scheduling/v1alpha1" ``` The paired `sigs.k8s.io/controller-runtime` minor (microsoft#2324, `0.23` → `0.24`, which requires k8s `v0.36`) fails the same way. This extends the group to `minor` updates so the whole lockstep set ships as one PR. Majors stay excluded — k8s.io core modules are perpetually `v0.x`, so the release train is always a minor. ## Related Issue N/A — follow-up from reviewing failing dependabot updates. ## Checklist - [x] I have read the [contributing documentation](https://retina.sh/docs/Contributing/overview). - [x] I signed and signed-off the commits (`git commit -S -s ...`). - [x] I have correctly attributed the author(s) of the code. - [x] I have tested the changes locally. - [x] I have followed the project's style guidelines. - [ ] I have updated the documentation, if necessary. - [ ] I have added tests, if applicable. (N/A — dependabot config.) ## Screenshots (if applicable) or Testing Completed YAML parses clean; dependabot validates the config on its next scheduled run — config-only change. ## Additional Notes After this merges, close microsoft#2329 and microsoft#2324; the next daily gomod run will regenerate them as a single grouped `k8s` PR containing the coherent `v0.36` set. Signed-off-by: Quang Nguyen <nguyenquang@microsoft.com>
Laksh (lakshk98)
pushed a commit
to lakshk98/retina
that referenced
this pull request
Aug 4, 2026
# Description The `k8s` dependabot group only covers `patch` updates, so k8s release trains (`v0.35` → `v0.36` across `k8s.io/api`, `apimachinery`, `client-go`, `kubectl`, `metrics`, …) arrive as individual PRs. Those modules version in lockstep, so a lone bump is unresolvable — microsoft#2329 has been failing dependency resolution for weeks: ``` k8s.io/metrics | dependency_file_not_resolvable | "go: ...k8s.io/kubectl/pkg/scheme imports k8s.io/api/scheduling/v1alpha1: module k8s.io/api@latest found (v0.36.2), but does not contain package k8s.io/api/scheduling/v1alpha1" ``` The paired `sigs.k8s.io/controller-runtime` minor (microsoft#2324, `0.23` → `0.24`, which requires k8s `v0.36`) fails the same way. This extends the group to `minor` updates so the whole lockstep set ships as one PR. Majors stay excluded — k8s.io core modules are perpetually `v0.x`, so the release train is always a minor. ## Related Issue N/A — follow-up from reviewing failing dependabot updates. ## Checklist - [x] I have read the [contributing documentation](https://retina.sh/docs/Contributing/overview). - [x] I signed and signed-off the commits (`git commit -S -s ...`). - [x] I have correctly attributed the author(s) of the code. - [x] I have tested the changes locally. - [x] I have followed the project's style guidelines. - [ ] I have updated the documentation, if necessary. - [ ] I have added tests, if applicable. (N/A — dependabot config.) ## Screenshots (if applicable) or Testing Completed YAML parses clean; dependabot validates the config on its next scheduled run — config-only change. ## Additional Notes After this merges, close microsoft#2329 and microsoft#2324; the next daily gomod run will regenerate them as a single grouped `k8s` PR containing the coherent `v0.36` set. Signed-off-by: Quang Nguyen <nguyenquang@microsoft.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
2 participants
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.
Description
The
k8sdependabot group only coverspatchupdates, so k8s release trains (v0.35→v0.36acrossk8s.io/api,apimachinery,client-go,kubectl,metrics, …) arrive as individual PRs. Those modules version in lockstep, so a lone bump is unresolvable — #2329 has been failing dependency resolution for weeks:The paired
sigs.k8s.io/controller-runtimeminor (#2324,0.23→0.24, which requires k8sv0.36) fails the same way. This extends the group tominorupdates so the whole lockstep set ships as one PR. Majors stay excluded — k8s.io core modules are perpetuallyv0.x, so the release train is always a minor.Related Issue
N/A — follow-up from reviewing failing dependabot updates.
Checklist
git commit -S -s ...).Screenshots (if applicable) or Testing Completed
YAML parses clean; dependabot validates the config on its next scheduled run — config-only change.
Additional Notes
After this merges, close #2329 and #2324; the next daily gomod run will regenerate them as a single grouped
k8sPR containing the coherentv0.36set.