Closed
Conversation
Member
|
I am not sure if we need a changelog for it. |
Member
|
I agree we don't need a changelog. We also wouldn't have created one if this had been opened by renovate. |
Member
|
#6829 is merged |
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.
Fix https://pkg.go.dev/vuln/GO-2025-3487 by bump
golang.org/x/cryptoto v0.35.0Waiting for #6853 to be merged to prevent generating the
toolchaindirective in go mod. It seemsgo mod tidywould add thetoolchaindirective if thegodirective is needed to be changed. And, thegolang.org/x/crypto:v0.35.0needs Go1.23. https://cs.opensource.google/go/x/crypto/+/master:go.mod;l=3After #6853 is merged, it is now good. No more automatic added
godirective aftergo mod tidy. Not sure if it is a bug of Go or not 🤷♂️.