From 75039d45b0e09c544fd5995d2f9ca83f5dbc96b1 Mon Sep 17 00:00:00 2001 From: Martin Pluskal Date: Mon, 17 Aug 2026 09:34:13 +0200 Subject: [PATCH] docs: refresh the rmcp reference-tree version to 3.1.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- docs/DESIGN.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/DESIGN.md b/docs/DESIGN.md index a0d85e5..8ed4831 100644 --- a/docs/DESIGN.md +++ b/docs/DESIGN.md @@ -1216,7 +1216,7 @@ Decisions, all deliberate: ## rmcp 3.1 usage notes Reference source is the rmcp this workspace pins, unpacked in the local -registry: `~/.cargo/registry/src/*/rmcp-3.1.1/` — today's version, and the +registry: `~/.cargo/registry/src/*/rmcp-3.1.2/` — today's version, and the directory holding the `rmcp` package's `manifest_path` in `cargo metadata --format-version 1` on any day, so it follows `Cargo.lock` rather than a copy of it and is by construction the source this build compiles against. Every rmcp @@ -1226,8 +1226,8 @@ routing traps), `handler/server/router/tool.rs` (`ToolRouter`, incl. `remove_route` / `has_route` — I13), `model.rs` and `model/serde_impl.rs` (`InitializeResult`, the `_meta` strip), `service.rs` (the serve loop); the `#[tool_router]` / `#[tool_handler]` expansions are in the sibling -`rmcp-macros-3.1.1` tree. The published crate carries no `examples/` — those -live upstream at the `rmcp-v3.1.1` tag — but for how this server is actually +`rmcp-macros-3.1.2` tree. The published crate carries no `examples/` — those +live upstream at the `rmcp-v3.1.2` tag — but for how this server is actually wired, `server.rs` and `main.rs` are the reference. - `rmcp = { version = "3.1", features = ["server", "macros", "transport-io", "transport-streamable-http-server"] }`