chore(ci): refresh Go toolchain pins to 1.25.14/1.26.6; bump grpc to v1.82.1 - #201
Merged
Merged
Conversation
…v1.82.1 The Go vulnerability database gained GO-2026-6090 and GO-2026-5972 (crypto/tls post-handshake messages, encoding/asn1 recursion) fixed in go1.26.6/go1.25.14, and GO-2026-5856 (ECH privacy leak) fixed in go1.26.5. Every module's govulncheck step started failing on these stdlib findings with no code change; bump the workflow toolchain pins so CI scans against patched stdlib. transport: google.golang.org/grpc v1.81.1 -> v1.82.1 clears GO-2026-6061, the one module-level finding (verified locally: govulncheck clean under go1.26.6, race tests green).
Clears the module-level govulncheck finding (GO-2026-6061 family) that the toolchain refresh alone cannot fix: pubsub's gRPC transport symbols are called from Adapt/Publish. Verified locally: govulncheck clean under go1.26.6, race tests green.
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.
Unblocking PR — repo-wide govulncheck breakage (pre-existing)
Every open PR's
gateis red: govulncheck steps acrosssink/*,source/jetstream,source/cloudevents,examples/sourcedrive,source/kafka, and the workspacevulnjob began failing on newly published Go standard-library vulnerabilities — no code change involved:Plus one genuine module-level finding: GO-2026-6061 in
google.golang.org/grpc@v1.81.1(transport), fixed in v1.82.1.Changes
.github/workflows/*.yml: toolchain pins1.26.4 → 1.26.6,1.25.11 → 1.25.14(comment in test.yml updated too).transport/go.mod:google.golang.org/grpc v1.81.1 → v1.82.1(+ transitive genproto bump).Local evidence
GOTOOLCHAIN=go1.26.6 go run govulncheck@v1.3.0 ./...intransport: 0 vulnerabilities affecting your code.sink/cloudwatchandexamples/sourcedrive: 0.GOTOOLCHAIN=go1.25.14 ...insource/kafka: 0.transport:go build/vet/test -race ./...green on grpc v1.82.1.This must merge before any feature PR can show a green
gate.