Update k8s dependencies to get rid of indirect mergo dependency #74
+19
−20
Conversation
This file contains 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
jaredoconnell
approved these changes
Jan 28, 2025
dbutenhof
approved these changes
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes introduced with this PR
This PR was generated by running
go get k8s.io/[email protected]and thengo get -t ./... && go mod tidy. It updates the direct dependencies on thek8s.iopackages to the next minor version. This has the highly desirable effect of removing the indirect dependency on themergopackage, which has caused so much inconvenience. (I'm not sure why the Renovate bot never proposed this update. 😢 Thanks so much to @mfleader, for pointing this out!!)By contributing to this repository, I agree to the contribution guidelines.