Repository navigation
Move to golang.org/x/net v0.62.0 - #55
Merged
Merged
Conversation
govulncheck reports GO-2026-6860 and GO-2026-6866 in x/net v0.60.0. Nothing here calls the affected code, but v0.62.0 fixes both, so the release goes out clean.
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.
This moves shield to golang.org/x/net v0.62.0 before the v1.9.1 release.
govulncheck reports GO-2026-6860 and GO-2026-6866 in x/net v0.60.0. Nothing in shield calls the affected code, so CI passes either way, but v0.62.0 fixes both and the release should go out clean. Weave does call it, through its HTML loader, and gets the same bump in its own PR.
Build, vet and the full test suite pass.