docs: refresh the rmcp reference-tree version to 3.1.2 - #101
Merged
Conversation
PR #98 bumped rmcp 3.1.1 -> 3.1.2, which left three version strings in the "rmcp 3.1 usage notes" preamble naming a tree that no longer exists locally: the registry path, the sibling rmcp-macros tree, and the upstream tag the missing examples/ live at. The first of those also called 3.1.1 "today's version", which the bump made false. The paragraph is built to survive this — it tells the reader to resolve the directory from the rmcp package's manifest_path in cargo metadata, so it follows Cargo.lock rather than a copy of it — and no claim resting on that tree changed: the 3.1.1...3.1.2 delta touches only client-side transport (auth.rs, client_side_sse.rs, reqwest/streamable_http_client.rs), none of tower.rs, model.rs, service.rs or handler/server/router/tool.rs. So this is the illustrative version string catching up, not a revisit of the notes.
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
1 participant
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.
Follow-up to #98, which bumped
rmcp3.1.1 → 3.1.2.Three version strings in the "rmcp 3.1 usage notes" preamble still named a
tree that no longer exists in the local registry — the registry path itself,
the sibling
rmcp-macrostree, and the upstream tag the absentexamples/live at. The registry-path sentence additionally called 3.1.1 "today's
version", which the bump made false.
Confirmed the real directories are now
rmcp-3.1.2/rmcp-macros-3.1.2(resolved from the
manifest_pathof each package incargo metadata --format-version 1).Why this is only a version-string refresh
The paragraph is deliberately built to survive a bump: it tells the reader to
resolve the directory from
cargo metadataso it followsCargo.lockratherthan a copy of it. Nothing the notes rest on changed — the entire
rmcp-v3.1.1...rmcp-v3.1.2delta is client-side:transport/auth.rstransport/common/client_side_sse.rstransport/common/reqwest/streamable_http_client.rsNone of
transport/streamable_http_server/tower.rs,handler/server/router/tool.rs,model.rs/model/serde_impl.rsorservice.rs— the four modules the notes actually cite — is touched. So theStreamableHttpServerConfigfield table stands,skips_the_handshakeremainsthe thing keeping a client that names a legacy revision off the handshake-free
path, and
DEFAULT_PROTOCOL_VERSIONis unaffected (upstream #1105, which movesProtocolVersion::LATEST, still has not landed). rmcp's client half is adev-dependency here.
Docs-only; no code or test changes.