chore: update LATEST_PROTOCOL_VERSION to 2025-11-25 #1715
Merged
+3
−3
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
felixweinberger
force-pushed
the
fweinberger/update-protocol-version
branch
from
f1ff416 to
afe8e37
Compare
maxisbey
approved these changes
Dec 2, 2025
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.
Updates
LATEST_PROTOCOL_VERSIONto2025-11-25and adds2025-06-18toSUPPORTED_PROTOCOL_VERSIONS.Motivation and Context
The protocol version 2025-11-25 was released but the SDK constants were not updated.
How Has This Been Tested?
ruff formatandruff check- passedpytest tests/test_types.py- all 14 tests passedBreaking Changes
None - this is a backwards compatible change.
Types of changes
Checklist