-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps: Update golang.org/x/crypto to v0.31.0 to resolve high vulnerability #3839
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
8cd56c4
to
a1dcd11
Compare
/test pull-project-infra-lint /cc @dhiller - any reason we can't take this one in? |
…lity A high vulnerability has been raised against all golang/x/crypto versions before v0.31.0 - CVE-2024-45337[1] Update golang/x/crypto to v0.31.0 [1] https://www.cve.org/CVERecord?id=CVE-2024-45337 Signed-off-by: Brian Carey <[email protected]>
a1dcd11
to
1b5aa52
Compare
@dhiller rebased to drop the bazel related changes. |
@brianmcarey: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/cc |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What this PR does / why we need it:
A high vulnerability has been raised against all golang/x/crypto versions before v0.31.0 - CVE-2024-45337[1]
Update golang/x/crypto to v0.31.0
[1] https://www.cve.org/CVERecord?id=CVE-2024-45337
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
/cc @dhiller
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: