Follow-ups to #1610: de-draft 2026-07-28 terminology, renumber error codes, ProtocolVersion floor (#1671)
This commit is contained in:
parent
90c853103d
commit
d6b1615988
1 changed files with 785 additions and 898 deletions
|
|
@ -36,11 +36,12 @@ McpClientOptions options = new()
|
|||
},
|
||||
};
|
||||
|
||||
// The default client now prefers the draft revision (probing with server/discover and falling back
|
||||
// to a legacy initialize handshake). The "initialize" and "sse-retry" scenarios specifically exercise
|
||||
// the legacy initialize handshake and SSE resumability (removed in draft) and strictly expect
|
||||
// initialize as the first message, so pin them to the latest stable version. Other scenarios run on
|
||||
// the draft default and exercise the server/discover probe plus the transparent legacy fallback.
|
||||
// The default client now prefers the 2026-07-28 protocol (probing with server/discover and
|
||||
// falling back to a legacy initialize handshake). The "initialize" and "sse-retry" scenarios
|
||||
// specifically exercise the legacy initialize handshake and SSE resumability (removed in the
|
||||
// 2026-07-28 protocol) and strictly expect initialize as the first message, so pin them to the
|
||||
// latest stable version. Other scenarios run on the 2026-07-28 default and exercise the
|
||||
// server/discover probe plus the transparent legacy fallback.
|
||||
if (scenario is "initialize" or "sse-retry")
|
||||
{
|
||||
options.ProtocolVersion = "2025-11-25";
|
||||
|
|
|
|||
Loading…
Reference in a new issue