Repository navigation
Bump Go to 1.26.10 and 1.27.3 to clear GO-2026-6809 - #613
Merged
Merged
Conversation
gerardrecinto
force-pushed
the
bump-go-1.26.10
branch
from
October 22, 2026 04:59
32b39bc to
31247f4
Compare
Gemini PR ReviewReviewed commit: This pull request updates the Go toolchain version across the codebase, Dockerfiles, and documentation from No actionable findings were identified:
|
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
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.
govulncheck and the Trivy image scan now fail on master with GO-2026-6809 in crypto/x509, found in go1.26.9 and fixed in go1.26.10. This moves every go.mod and go.work to 1.26.10, the Docker base images to golang:1.27.3 (bindings build image to 1.26.10), and the version mentions in the README and docs. Historical mentions in docs/INCIDENTS.md and the example lab notes are left as written.