chore: pin Go toolchain to 1.26.4 across all modules#164
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.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
1 participant
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.
GO-2026-5037 (crypto/x509) and GO-2026-5039 (net/textproto) are fixed in go1.26.4. The workspace and telemetry/datadog already had the toolchain pin; the remaining 46 modules did not, leaving them exposed when built standalone (as govulncheck does in CI).
Adds
toolchain go1.26.4immediately after thegodirective in every remaining go.mod. No language version or dependency changes.All 46 modules build clean with
GOWORK=off go build ./...; govulncheck reports no vulnerabilities on sink/kafka and source/kafka post-change.