Fix several go CVEs in release-1.13 [crypto,kubernetes,net]#565
Merged
amacaskill merged 1 commit intoGoogleCloudPlatform:release-1.3from Apr 16, 2025
Merged
Conversation
amacaskill
approved these changes
Apr 16, 2025
e7968a3 to
81a49cb
Compare
81a49cb to
fe20e80
Compare
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
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.
What type of PR is this?
What this PR does / why we need it:
This PR addresses security vulnerabilities in tag 1.3.5 and supersedes the missing/deleted 1.3.4 version. There was an unexplained deletion that disrupted automated version control flows and impacted component history. To continue cleanly from
v1.3.3, this tag includes the following go module upgrades:Module updates:
golang.org/x/crypto: v0.22.0 → v0.35.0k8s.io/kubernetes: v1.29.4 → v1.29.14golang.org/x/net: v0.24.0 → v0.36.0Which issue(s) this PR fixes:
Does not fix but is in relation to the following bug -
https://b.corp.google.com/issues/407850643
Special notes for your reviewer:
Does this PR introduce a user-facing change?: