Repository navigation
Update gRPC to 1.83.2 security patch - #201
Merged
PaxMachinaOne merged 1 commit intoOct 16, 2026
Merged
Conversation
novatechflow
marked this pull request as ready for review
October 16, 2026 17:35
PaxMachinaOne
approved these changes
Oct 16, 2026
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
2 participants
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.
gRPC 1.83.1 remains affected by the xDS missing
:authority/Hostcrash advisory on the 1.83.x line. Upgrade to 1.83.2 in the platform, SQL processor, and Iceberg processor, resolving Dependabot alerts #155, #156, and #157 (GHSA-2v4p-qf9q-27wj).Refresh the required transitive Go dependencies and module checksums. All three effective module graphs select gRPC 1.83.2.
Validation: Go coverage gate passes at 85.8% (85% floor); full
make commit-checkpassed, including Go vet/race, nested modules, SDK tests, fuzzing, and the local CodeQL gate. CI Go tests, coverage, and all CodeQL scans have also passed; operator conformance is still running. Docker-backed e2e tests are unavailable locally because Docker is not running.