Repository navigation
Fix govulncheck failures by updating Go to 1.27.2 - #1031
Merged
Merged
Conversation
govulncheck now reports GO-2026-6617, GO-2026-6613 and GO-2026-6612 in net/http and http2. golangci-lint 2.13.1 cannot read Go 1.27.2 export data, so update it to 2.14.0. Amp-Thread-ID: https://ampcode.com/threads/T-b6c2f8a1-bb8c-41d0-891d-a49901c22546 Co-authored-by: Amp <amp@ampcode.com>
SorchaAbel
approved these changes
Oct 9, 2026
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.
Why
govulnchecknow fails onmainand on every PR, for example #1030:main's last green build ran before these advisories were published.What
golang.org/x/net0.58.0 → 0.60.0export data version 5 is greater than maximum supported version 4). 2.14.0 lints cleanly, with no new findings.govulnchecknow reportsYour code is affected by 0 vulnerabilities.