chore(ci): bump go 1.25.10 -> 1.25.11 (fix stdlib vulns)#27
Conversation
Resolves stdlib vulns flagged by govulncheck: GO-2026-5039 (net/textproto error escaping) and GO-2026-5037 (crypto/x509 hostname parsing), both fixed in go1.25.11. All CI jobs read go-version-file: go.mod, so this bumps the toolchain everywhere (build/test/lint/vuln/e2e/release). Dockerfile uses golang:1.25-alpine which already tracks the latest 1.25.x.
|
Warning Review limit reached
More reviews will be available in 56 minutes and 47 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ 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 |
Bumps the Go toolchain to 1.25.11 to clear the two stdlib vulnerabilities govulncheck flags on 1.25.10:
GO-2026-5039— arbitrary inputs unescaped innet/textprotoerrors (reached viawebsocket.Dialer.DialContext).GO-2026-5037— inefficient candidate hostname parsing incrypto/x509.Both are Fixed in go1.25.11. All CI jobs use
go-version-file: go.mod, so the singlego.modbump applies the toolchain to build/test/lint/vuln/e2e/release. The Dockerfile'sgolang:1.25-alpinealready tracks the latest 1.25.x.Verified
go build ./...clean on go1.25.11 locally. Expect thevulncheck to go green here.