chore: bump Go 1.25.12 -> 1.25.13 + x/net v0.55.0 (govulncheck) - #159
Merged
Conversation
…heck) Go 1.25.13 shipped security fixes; six advisories with reachable call paths now flag the 1.25.12 stdlib (GO-2026-6218 net/url, GO-2026-6091 html/template, GO-2026-6090 crypto/tls, GO-2026-6089 net/http, GO-2026-5972 encoding/asn1) plus GO-2026-5026 in x/net's idna. CI reads the toolchain from go.mod, so every master push fails Security Scanning until the directive moves. Verified with GOTOOLCHAIN=go1.25.13 govulncheck ./... -> 0 affecting vulnerabilities; full test suite green under the same toolchain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
What
go.modgodirective: 1.25.12 → 1.25.13 (CI installs from this viago-version-file)golang.org/x/net(indirect): v0.53.0 → v0.55.0 (x/text and x/tools move as its deps)Why
Go 1.25.13 shipped security fixes and six advisories now flag master's build with reachable call paths, so Security Scanning's govulncheck step fails every master push (first tripped by #157's merge run — same time-triggered pattern as the nanoid advisory, unrelated to that PR's content):
net/url, GO-2026-6091html/template, GO-2026-6090crypto/tls, GO-2026-6089net/http, GO-2026-5972encoding/asn1x/netidna, fixed by v0.55.0 + the stdlib bumpVerification
GOTOOLCHAIN=go1.25.13 govulncheck ./...— 0 affecting vulnerabilities (replicates CI, which resolves the toolchain from go.mod; a plain local run scans the dev toolchain's stdlib instead and still reports the 1.26.5-line findings, fixed separately in 1.26.6)npm audit --omit=dev --audit-level=highinweb/— 0 vulnerabilitiesgo test ./...under go1.25.13 — all packages passgo build ./...— clean🤖 Generated with Claude Code