Skip to content

Fix govulncheck failures by updating Go to 1.27.2 - #1031

Merged
lox merged 1 commit into
mainfrom
bump-go-1.27.2
Oct 9, 2026
Merged

lox merged 1 commit into
mainfrom
bump-go-1.27.2

Conversation

@lox

@lox lox commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Why

govulncheck now fails on main and on every PR, for example #1030:

Vulnerability #1: GO-2026-6617   Found in: net/http/internal/http2@go1.27.1  Fixed in: go1.27.2
Vulnerability #2: GO-2026-6613   Found in: net/http@go1.27.1                 Fixed in: go1.27.2
Vulnerability #3: GO-2026-6612   Found in: golang.org/x/net@v0.58.0          Fixed in: v0.60.0
[vulncheck] ERROR task failed

main's last green build ran before these advisories were published.

What

  • Go 1.27.1 → 1.27.2
  • golang.org/x/net 0.58.0 → 0.60.0
  • golangci-lint 2.13.1 → 2.14.0. With Go 1.27.2, 2.13.x fails to typecheck the standard library (export data version 5 is greater than maximum supported version 4). 2.14.0 lints cleanly, with no new findings.

govulncheck now reports Your code is affected by 0 vulnerabilities.

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>
@lox
lox requested review from a team as code owners October 9, 2026 06:55
@lox
lox merged commit 5c0196b into main Oct 9, 2026
2 checks passed
@lox
lox deleted the bump-go-1.27.2 branch October 9, 2026 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants