ci: bump pinned Go to 1.25.12 (GO-2026-5856)#82
Merged
Merged
Conversation
govulncheck now fails every PR: GO-2026-5856 (Encrypted Client Hello privacy leak in crypto/tls) is present in go1.25.11 and fixed in go1.25.12. Bump the pinned toolchain across all workflows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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 fails every PR since GO-2026-5856 (Encrypted Client Hello privacy leak in
crypto/tls) was published: it affects go1.25.11 (our pinned toolchain) and is fixed in go1.25.12. Reachable via the API server / cloud registry / freshness fetcher call paths, so the finding is real, not noise.Bumps
GO_VERSION/go-versionin all six workflows that pin it (ci, codeql, release-artifacts, stability-gate, kernel-freshness, profile-catalog-maintenance).Unblocks #81.
🤖 Generated with Claude Code