fix(deps): bump Go 1.25.10 -> 1.25.11 for new stdlib CVEs#606
Merged
Conversation
A fresh govulncheck DB update flagged two new stdlib vulnerabilities in go1.25.10, re-blocking the PR queue one day after #602: - GO-2026-5039: net/textproto - GO-2026-5037: crypto/x509 Both fixed in go1.25.11. Bumps the go directive and the Dockerfile go-builder image in lockstep (CI reads go-version-file: go.mod; the Docker build pins the builder explicitly and would otherwise fail on the version mismatch). Verified: go build, go vet, and `GOTOOLCHAIN=go1.25.11 govulncheck ./...` reports "No vulnerabilities found". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the project’s Go toolchain patch version to address newly reported Go stdlib vulnerabilities, keeping CI (which installs Go via go.mod) and the Docker build (which pins the builder image) in sync.
Changes:
- Bump
godirective ingo.modfrom1.25.10to1.25.11. - Bump Docker
go-builderbase image fromgolang:1.25.10-alpinetogolang:1.25.11-alpine.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| go.mod | Updates the Go toolchain version used by CI via go-version-file: go.mod. |
| Dockerfile | Pins the builder stage to Go 1.25.11 to match the go.mod directive and ensure patched stdlib in container builds. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
A fresh govulncheck DB update (one day after #602) flagged two new stdlib vulnerabilities in go1.25.10, re-blocking the entire PR queue — main itself, the remaining Dependabot PRs (#588/#591/#596), and release #603 all fail
Vulnerability Check:Pure toolchain bump — no module changes. Bumps the
godirective and the Dockerfilego-builderimage in lockstep (CI readsgo-version-file: go.mod; the Docker build pins the builder explicitly and fails on a version mismatch otherwise).Verification (local)
go build ./.../go vet ./...— cleanGOTOOLCHAIN=go1.25.11 govulncheck ./...— "No vulnerabilities found"Once merged, rebasing #588/#591/#596 onto main clears their vuln check, and #603 (v0.6.5) can be cut.
🤖 Generated with Claude Code