build(deps): bump rmcp from 1.8.0 to 2.2.0#9
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [rmcp](https://github.com/modelcontextprotocol/rust-sdk) from 1.8.0 to 2.2.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-v1.8.0...rmcp-v2.2.0) --- updated-dependencies: - dependency-name: rmcp dependency-version: 2.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
8 tasks
AnderEnder
added a commit
that referenced
this pull request
Jul 10, 2026
…y fixes) (#11) * build(deps): update dependencies within semver ranges Resolves 3 security advisories via cargo update (all within existing Cargo.toml ranges): - quick-xml 0.37.5 -> 0.41.0 (via feed-rs 2.3.1 -> 2.4.0) fixes RUSTSEC-2026-0194 and RUSTSEC-2026-0195 (both high, 7.5) - quinn-proto 0.11.14 -> 0.11.16 (via reqwest) fixes RUSTSEC-2026-0185 (high) - anyhow 1.0.102 -> 1.0.103 fixes RUSTSEC-2026-0190 (unsound) Also bumps clap_complete 4.6.5 -> 4.6.7 and assorted transitive crates. cargo audit clean; build, test, clippy -D warnings all pass. * build(deps): upgrade rmcp 1.x -> 2.2.0 Major bump of the MCP SDK. rmcp 2.0 aligns model types with the MCP 2025-11-25 spec; the only source change needed was the Content -> ContentBlock rename (unified content model, replacing the Annotated<T> wrapper). CallToolResult::success/error and the structured_content field are unchanged, so the tool router, output schemas, annotations, and structured-content behavior all carry over untouched. Verified end-to-end against `rss mcp`: initialize negotiates protocol 2025-11-25, tools/list advertises all four tools with output schemas, and a live fetch_feed tools/call returns structuredContent over the wire. build, test (99 tests), and clippy -D warnings all pass. Supersedes Dependabot PR #9.
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 2.2.0.
Release notes
Sourced from rmcp's releases.
... (truncated)
Commits
5195776chore: release v2.2.0 (#953)6dd7b85chore(deps): update p256 requirement from 0.13 to 0.14 (#959)a037935fix: pass client conformance suite (#960)dbda50cfix: don't respond to cancelled requests (#957)45f2f72fix: fail orphaned streamable HTTP responses on reinit (#914)95490fafeat: reject auth servers lacking S256 PKCE support (#955)bdf0c32fix: address 2025-11-25 conformance audit findings (#951)8e44af4chore: release v2.1.0 (#950)4833ec7fix(transport): make AsyncRwTransport::receive cancel-safe (#941) (#947)5837e22fix(auth): preserve refresh_token when refresh response omits it (#949)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)