You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Client] Probe for 2026-07-28 and fall back to the handshake - #547
A client configured with 2026-07-28 probes with server/discover and falls back to initialize on 2025-11-25 unless the server proves to be modern, following the backward compatibility section of the spec - setFallbackProtocolVersion() picks the revision, null makes it modern-only
HTTP refusals and a dead stdio server fail the request at once instead of waiting out the timeout - a lost stdio connection fails the probe instead of falling back, flagged via the new TransportInterface::CONNECTION_LOST key in the error data
On a modern connection setLoggingLevel() rides on every request, ping() uses server/discover and the roots notification is skipped
The default stays 2025-11-25, the bump itself is #537.
Allow modern clients to skip removed notifications without capability checks
src/Client.php:380
The modern no-op is reached only after the roots.listChanged capability guard, so a modern client built with the default capabilities still throws instead of skipping this removed notification. Check the connection/era first, then enforce the legacy capability only for handshake-era connections.
Prevent uncorrelated error bodies from overriding probe results
src/Client/Transport/HttpTransport.php:260
Once the same-ID/well-formed check above fails, this body may be malformed or belong to another request, but its error code and data are still reassigned to the current request. For example, an id-less or mismatched -32022 body can make a probe fail as an authoritative modern-version refusal instead of falling back. Treat every uncorrelated body as the generic HTTP refusal; only the validated branch above should preserve JSON-RPC error details.
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
2026-07-28All issues and PRs related to the spec release 2026-07-28ClientIssues & PRs related to the Client component
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.
Follows #546, split out of #537.
2026-07-28probes withserver/discoverand falls back toinitializeon2025-11-25unless the server proves to be modern, following the backward compatibility section of the spec -setFallbackProtocolVersion()picks the revision,nullmakes it modern-onlyTransportInterface::CONNECTION_LOSTkey in the error datasetLoggingLevel()rides on every request,ping()usesserver/discoverand the roots notification is skippedThe default stays
2025-11-25, the bump itself is #537.