build(deps): bump rmcp from 1.8.0 to 3.1.2 - #246
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [rmcp](https://github.com/modelcontextprotocol/rust-sdk) from 1.8.0 to 3.1.2. - [Release notes](https://github.com/modelcontextprotocol/rust-sdk/releases) - [Changelog](https://github.com/modelcontextprotocol/rust-sdk/blob/main/release-plz.toml) - [Commits](modelcontextprotocol/rust-sdk@rmcp-v1.8.0...rmcp-v3.1.2) --- updated-dependencies: - dependency-name: rmcp dependency-version: 3.1.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/rmcp-3.1.2
branch
from
August 13, 2026 14:52
d92780d to
fbc5c83
Compare
shankar-gpio
added a commit
that referenced
this pull request
Aug 13, 2026
Two majors. The compile break is trivial — `stateful_mode` became
`legacy_session_mode` and now defaults to true, so the assignment is deleted
rather than renamed. Per SEP-2567 it only applies to protocol versions
< 2026-07-28 anyway; newer clients are served statelessly regardless.
The part that mattered does not fail to compile. rmcp 3.x added inbound
`Host` validation defaulting to ["localhost", "127.0.0.1", "::1"] — a DNS
rebinding guard aimed at servers running on a developer's own machine. This
server is the other kind: `--http` binds 0.0.0.0:8081, ships as
ghcr.io/goplasmatic/orion-cli, and is listed in the MCP registry for remote
clients. Taken silently, that default would have rejected every request
arriving under any name but loopback.
Measured rather than reasoned about, by building both ways and posting a
real `initialize` at each:
Host: localhost:8099 200 200
Host: mcp.example.com 403 200
default disable_allowed_hosts()
So `disable_allowed_hosts()` restores exactly the reachability rmcp 1.x had.
It weakens nothing that was previously enforced — there was no Host check
before — but it does decline a new protection, deliberately and in one
commented place rather than by omission.
The protection is worth having later. It needs an operator-supplied hostname
to mean anything, which means a repeatable `--allowed-host` flag and a
decision about breaking existing deployments that pass none. That is a
feature with a CLI surface, not a dependency bump, and not something to slip
into 1.0 unannounced.
Contributor
Author
|
Looks like rmcp is up-to-date now, so this is no longer needed. |
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
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.
Bumps rmcp from 1.8.0 to 3.1.2.
Release notes
Sourced from rmcp's releases.
... (truncated)
Commits
02c62aechore: release v3.1.2 (#1148)c345078fix(auth): map 401/403 challenges on the SSE GET stream (#1152)f8e6382chore(deps): bump taiki-e/install-action from 2.85.7 to 2.85.8 (#1153)8fb3e04chore(deps): bump github/codeql-action from 4.37.4 to 4.37.6 (#1154)3c8fb2afix(sse): loop instead of recursing when skipping SSE events (#1146)e150d4ffix(auth): preserve issuer trailing slash during discovery (#1145)9a3168achore(deps): bump taiki-e/install-action from 2.85.6 to 2.85.7 (#1139)baac607chore: release v3.1.1 (#1115)f57d585chore: upgrade darling and syn (#1138)07bcda2fix: emit cache hints from handler macros (#1120)