Skip to content

Commit 5e479ca

Browse files
committed
docs: drop cross-link whose anchor slug differs between checkers
The "client request timeouts" heading contains a leading-hyphen number, which GitHub-style slugging (markdownlint MD051) and python-markdown (the site build) render as different anchors, so any fragment link to it fails one of the two strict checks. Refer to the section in prose instead. No-Verification-Needed: doc-only change
1 parent 1873295 commit 5e479ca

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/migration.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -150,9 +150,9 @@ subtle ways (server-initiated messages stop arriving) instead of raising immedia
150150

151151
Retry and error-classification logic keyed to HTTP status codes needs a look too: through
152152
the SDK's client, timeouts and non-2xx responses surface as `MCPError` with JSON-RPC codes,
153-
not `408`s or `httpx.HTTPStatusError` — see
154-
[Client request timeouts now raise `-32001`](#client-request-timeouts-now-raise--32001-request_timeout-instead-of-408)
155-
and [Streamable HTTP: non-2xx responses now surface as per-request JSON-RPC errors](#streamable-http-non-2xx-responses-now-surface-as-per-request-json-rpc-errors).
153+
not `408`s or `httpx.HTTPStatusError` — see the client request timeouts section
154+
(`REQUEST_TIMEOUT`, `-32001`) under [Clients](#clients) and
155+
[Streamable HTTP: non-2xx responses now surface as per-request JSON-RPC errors](#streamable-http-non-2xx-responses-now-surface-as-per-request-json-rpc-errors).
156156

157157
The SDK's own auth providers made the same move: `OAuthClientProvider`,
158158
`ClientCredentialsOAuthProvider`, `PrivateKeyJWTOAuthProvider`, and

0 commit comments

Comments
 (0)