Repository navigation
chore(deps): bump rmcp from 2.2.0 to 3.1.0 - #673
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [rmcp](https://github.com/modelcontextprotocol/rust-sdk) from 2.2.0 to 3.1.0. - [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-v2.2.0...rmcp-v3.1.0) --- updated-dependencies: - dependency-name: rmcp dependency-version: 3.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Contributor
ecp impact cache (0 symbols) — internal, used by
|
Owner
|
Superseded by #676, which lands the same rmcp 3.1.0 bump together with the source migration it needs. The compile break is |
coseto6125
added a commit
that referenced
this pull request
Aug 5, 2026
* chore(deps): migrate to rmcp 3.1 and refresh the lockfile Dependabot could not land this one on its own — #668 (3.0.0), #670 (3.0.1) and #673 (3.1.0) all stalled on the same compile break. rmcp 3.0 tracks MCP 2026-07-28. The only break reaching this crate is SEP-2322 MRTR: `ServerHandler::call_tool` now returns `CallToolResponse` (`Complete` / `InputRequired` / `Task`) instead of `CallToolResult`. `ecp mcp serve` is spawn-mode only, so every call runs the subcommand to completion and resolves as `Complete`; the migration is the `From<CallToolResult>` conversion at the single return site. The rest of the 3.0 breaking list is inapplicable here: sessionless Streamable HTTP, the stateless discovery lifecycle, subscriptions and the tasks extension are HTTP-transport or client-side concerns, and this server is stdio + `serve_server`. `cargo update` alongside brings the rest of the tree to latest compatible. * refactor: use regex! for the two hand-rolled lazy Regex accessors regex 1.13 ships a `regex!` macro that expands to exactly the `static Lazy<Regex>` shape these two accessors were writing by hand. Semantics are identical (process-lifetime lazy compilation), so this is boilerplate removal, not a perf change. Left alone deliberately: the module-level named statics in `fetch_shape/` carry doc comments and long patterns. Inlining those into their call sites would bury a 100-char pattern inside a `for` header and drop the documentation. The `regex` floor moves to 1.13.0 in the two crates using the macro.
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 2.2.0 to 3.1.0.
Release notes
Sourced from rmcp's releases.
... (truncated)
Commits
1f9358echore: release v3.1.0 (#1090)1cf6debdocs: document the ping utility with examples (#1106)00bcf13fix(model): decode metadata-bearing input-required results affecting mrtr (#1...65f05e9feat: classify authorization-required errors (#1056)3240b6edocs: complete Tier 1 feature docs and finalize roadmap (#1101)def31f0chore(deps): bump github/codeql-action from 4 to 4.37.3 (#1100)570c478chore(deps): bump taiki-e/install-action from 2 to 2.85.2 (#1099)983a137feat: add strict stateless protocol metadata validation (#1091)58b136ffix: require metadata for modern HTTP requests (#1089)d272389fix: honor supported_protocol_versions when negotiating initialize (#1093)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)