Repository navigation
fix(go): clear the govulncheck findings and track supported Go releases - #126
Merged
Merged
Conversation
The 1.26.x leg resolved to Go 1.26.8 from the runner toolcache while the nine standard library findings are fixed in 1.26.9, released today. setup-go now runs with check-latest so a patch release is picked up as soon as it ships. golang.org/x/net moves from v0.58.0 to v0.61.0 (fixed from v0.60.0). Every patched x/net requires go 1.26.0, so the module directive follows and the matrix becomes 1.26.x / 1.27.x. Go 1.25 stopped receiving security fixes when 1.27 shipped, so nothing supported is dropped. Static analysis stays on the 1.26.x leg: staticcheck v0.8.1 cannot read Go 1.27 export data yet.
JeanExtreme002
added a commit
that referenced
this pull request
Oct 9, 2026
Patch release so the next Go module tag requires golang.org/x/net v0.61.0 (#126) instead of a version with open advisories. Python and Node move with it because verify-versions refuses a release whose three declared versions disagree.
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.
Why
The Go Package workflow failed on the 1.6.2 bump (runs 37953153947 and 37953225503) at the
make securitystep on the 1.26.x leg. govulncheck reported nine standard library findings (GO-2026-6603 through GO-2026-6617, innet/http,net/textprotoandcrypto/tls) plus the matchinggolang.org/x/netadvisories.Two things lined up:
1.26.xto Go 1.26.8 from its toolcache. The fixes landed in 1.26.9, released today, butsetup-goonly looks past the cache whencheck-latestis set.go.modrequiredgolang.org/x/net v0.58.0; the fix is in v0.60.0.What
setup-gonow runs withcheck-latest: true, so a new patch release is picked up as soon as it ships instead of whenever the runner image refreshes.golang.org/x/netbumped to v0.61.0 (x/textfollows to v0.43.0). Every patched x/net release requiresgo 1.26.0, so the module directive moves from 1.25.0 to 1.26.0 and the matrix becomes 1.26.x / 1.27.x. Go 1.25 left the two-release support window when 1.27 shipped, so no supported toolchain is dropped. Thego-1.25+badges in the READMEs and docs now say 1.26+.Verification
Both legs reproduced locally with the real toolchains via
GOTOOLCHAIN:go mod tidyleavesgo.modandgo.sumunchanged.Note on consumers
Raising the module directive to 1.26.0 means
go getof the next tagged Go module version needs Go 1.26 or newer. This does not affectgo/v1.6.2, which is already tagged.