chore(deps): bump Go to 1.26.4 (GO-2026-5039, GO-2026-5037)#4
Conversation
govulncheck flagged two stdlib vulns present in go1.26.3, both fixed in go1.26.4: GO-2026-5039 (net/textproto unescaped input in errors) and GO-2026-5037 (crypto/x509 inefficient hostname parsing). Bump the go directive so setup-go provisions the fixed toolchain.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesGo Toolchain Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the Go version in the go.mod file from 1.26.3 to 1.26.4. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Why
The
vulnCI job (govulncheck) fails on the currentgo 1.26.3toolchain due to two Go standard-library vulnerabilities, both fixed in go1.26.4:net/textprotocrypto/x509Detection traces run through
main.gofmt.Printf/fmt.Println(the--version/--helppaths), so practical impact is minimal, but govulncheck exits non-zero and the job is red.What
Bump the
godirective ingo.modto1.26.4. Withgo-version-file: go.modin CI,setup-gothen provisions the fixed toolchain.Verification
Locally on go1.26.4:
go vet ./...,go test ./..., andgovulncheck ./...all pass —No vulnerabilities found.This is independent of #3 (actions/checkout bump); that PR was red for the same
vulnreason. Once this merges, rebasing #3 onto main turns it green.Summary by CodeRabbit