Release v1.3.0 (#1566)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Jeff Handley 2026-05-07 18:32:13 -07:00 • committed by GitHub
commit 2ce15f4c8a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -279,7 +279,7 @@ This is entirely automatic — you don't need to manage the session ID yourself.
The server can terminate a session at any time — due to idle timeout, max session count exceeded, explicit shutdown, or any server-side policy. When this happens, subsequent requests with that session ID receive HTTP `404`. The client detects this and:
1. Wraps the failure in a `TransportClosedException` with <xref:ModelContextProtocol.Client.HttpClientCompletionDetails> containing the HTTP status code
1. Wraps the failure in a <xref:ModelContextProtocol.Client.ClientTransportClosedException> with <xref:ModelContextProtocol.Client.HttpClientCompletionDetails> containing the HTTP status code
2. Cancels all in-flight operations
3. Completes the <xref:ModelContextProtocol.Client.McpClient.Completion> task