Repository navigation
chore: sync protocol 1.4.7 datagram negotiation - #22
Merged
Merged
Conversation
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.
Synchronize the protobuf source and generated Python bindings with additive protocol 1.4.7 fields for independent native datagram channel negotiation. Existing fields and wire numbers are unchanged. Python does not opt in or gain QUIC support.
Validation: protoc regeneration; ruff lint/format; mypy; pytest (186 passed, 6 existing opt-in integration skips); wheel/sdist build; all six SDK/Engine request/response schemas agree.
No package version bump or publication. Future SDK distribution requires an Engine supporting 1.4.7 first; released 1.4.6 SDKs remain supported.