fix: Bump Go dependencies and Go version. - #2286
Merged
Merged
Conversation
Require Go 1.26.3. Update to latest (1.36.x) k8s.io deps amongst others. (cherry picked from commit 0871f7c)
github-actions
Bot
added
internal/pr-backport
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.
This pull request cherry-picks the changes from #2278 into release/v15
Addresses #2280 for #2279
WARNING!: to avoid having to resolve merge conflicts this PR is generated with 'git cherry-pick -X theirs'.
Please make sure to carefully inspect this PR so that you don't accidentally revert anything!
Copied from main PR:
Description
This updates the product to the latest Go version as well as the latest dependency versions so that we are on the most recent APIs/SDKs.
Testing
This is an overarching concern that may affect each resource differently.
No changes made break the interface of any resource (or compile checks would fail), and build stages pass.
The overarching test used to validate the provider release is the best way to validate this change, there is no specific test at this time which can validate this functionality otherwise.
Not a breaking change.