fix: bump Go toolchain to 1.26.7 to clear stdlib CVEs - #313
Merged
Conversation
govulncheck has been failing on develop since 2026-08-18, blocking every open PR. The failure is not caused by any code change — six standard library advisories landed in the Go vulnerability database, all fixed in go1.26.6: 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 GO-2026-5026 net/http (idna punycode) Every workflow resolves its Go version via setup-go with go-version-file: go.mod, which honours the toolchain directive, so the go1.26.5 pin was what CI actually built with. Bumping to go1.26.7 (the current latest patch) picks up the fixes everywhere at once. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.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
2 participants
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.
Problem
govulncheckis a required check ondevelop, and it has been failing since 2026-08-18 (the push that merged #309). Every open PR is blocked by it, including the Dependabot action bumps that have nothing to do with Go code.The failure is not caused by any change in this repo — six Go standard library advisories landed in the vulnerability database, all fixed in
go1.26.6:net/urlhtml/templatecrypto/tlsnet/httpencoding/asn1net/http(idna punycode)The govulncheck run on #303 confirms the toolchain in play:
Setup go version spec 1.26.5→go version go1.26.5 linux/amd64.Fix
Bump the
toolchaindirective ingo.modfromgo1.26.5togo1.26.7(current latest patch).Every workflow —
govulncheck,validate,acceptance,e2e— resolves its Go version throughsetup-gowithgo-version-file: go.mod, which honours thetoolchaindirective. So this single line fixes CI everywhere at once. Thegodirective stays at1.26.0; the minimum language version is unchanged, only the toolchain used to build.Verification
Self-proving: the
govulncheckcheck on this PR builds with the new toolchain. Green here means the CVEs are cleared.Follow-up
develophasstrict: true(require branches up to date before merging), so the other open PRs need a rebase after this lands — which also picks up the fix.