mcp: export ClientSessionOptions.ProtocolVersion - #1127
Merged
guglielmo-san merged 2 commits intoAug 3, 2026
Merged
Conversation
Allow clients to request a specific protocol version at Connect time. Empty continues to mean the latest supported version; negotiation is unchanged. Fixes modelcontextprotocol#1113
guglielmo-san
approved these changes
Aug 3, 2026
Contributor
|
This makes sense, thank you for the contribution |
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.
Summary
ClientSessionOptions.protocolVersionwas unexported and documented as test-only, so external consumers ofClient.Connectcould not request a specific protocol revision.This exports the field as
ProtocolVersionwith the same semantics:Usage
Testing
go test ./mcp/ -count=1(pass)Fixes #1113