Skip to content

build(deps): adopt rmcp 3.8.0 - #417

Merged
plusky merged 1 commit into
mainfrom
build/rmcp-3.8.0
Nov 2, 2026
Merged

plusky merged 1 commit into
mainfrom
build/rmcp-3.8.0

Conversation

@plusky

@plusky plusky commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Moves rmcp and rmcp-macros to 3.8.0, which changes only the streamable HTTP client (#1386, #1363). The binary compiles none of that, so stdio and HTTP replies are byte-identical across both locks, and DESIGN.md's stamps move to 3.8. The lock is Dependabot's and also carries rustix 1.1.6, which only the tests use through tempfile. Verified with the full workspace gates, cargo deny check, the local stamp-drift step, an OCR pass and an adversarial review that diffed the vendored sources, the feature graph and the served wire output; supersedes #415.

rmcp 3.8.0 changes only the streamable HTTP client: 429 and 5xx
responses surface as an HttpStatusError before the body is read
(#1386), and SSE reconnects stop on permanent GET errors (#1363). None
of it is compiled into the binary, whose rmcp features are server-side
only; the client arrives solely as a dev-dependency. The server half
and the macro sources are byte-identical to 3.7.0, and stdio and HTTP
replies were compared byte for byte across both locks, so the manifest
keeps asking for "3.6".

The lock is Dependabot's: rmcp and rmcp-macros as a matched pair, plus
rustix 1.1.6, which reaches only tempfile in the dev-dependencies.
DESIGN.md's stamps and the comments naming the version move with it,
except the sentence recording the 3.7 adoption measurement. One
re-stamped comment named rmcp's `sep_2322_supported`, renamed upstream
in 3.5.1; it now names `is_2026_07_28_or_later`.

Supersedes Dependabot #415.
@plusky
plusky merged commit aee5c07 into main Nov 2, 2026
19 checks passed
@plusky
plusky deleted the build/rmcp-3.8.0 branch November 2, 2026 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant