chore: update all crates to latest (incl. rmcp 1.x → 2.2.0, 3 security fixes)#11
Merged
Conversation
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.
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.
AnderEnder
changed the title
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
1 participant
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.
Summary
cargo outdated --root-deps-onlynow reports "All dependencies are up to date" — every direct dependency is at its latest release, including the one major bump (rmcp).cargo update).Security advisories resolved
cargo auditis now clean (0 vulnerabilities, was 3).Key package updates
Plus assorted transitive crate updates from
cargo update(bytes, h2, http, regex, rustls, uuid, zerocopy, wasm-bindgen, …).Breaking change resolved: rmcp 1.x → 2.2.0
rmcp 2.0 aligns its model types with the MCP 2025-11-25 spec. The only source change required was the
Content→ContentBlockrename (the unified content model replaces the oldAnnotated<T>wrapper).CallToolResult::success/::errorand the publicstructured_contentfield are unchanged, so the tool router, generated output schemas, tool annotations, and structured-content behavior all carried over untouched (invariants #7/#8 preserved).Verified end-to-end against
rss mcp:initializenegotiates protocol 2025-11-25tools/listadvertises all four tools with their output schemasfetch_feedtools/callreturnsstructuredContentover the wireSupersedes open Dependabot PRs
Test plan
cargo fmt --all --checkcargo clippy --all-targets -- -D warnings(clean)cargo build+cargo testfrom a clean slate — 99 tests passcargo build --release(fat LTO + panic=abort — the CI-uncovered gate) passescargo audit— 0 vulnerabilities (was 3)cargo outdated --root-deps-only— all up to date