Repository navigation
chore(deps): Bump rmcp from 1.8.0 to 2.2.0 - #38
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] <support@github.com>
dependabot
Bot
added
dependencies
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🔴 Changes requested0 actionable comment(s) · grounded on your code
⏱ 24s wall clock · 🤖 developerz.ai — automated review, running on your model and your box. |
![developerz-ai[bot]](https://avatars.githubusercontent.com/in/3783704?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review summary — 2 file(s), 0 finding(s).
Bumps rmcp 1.7→2.2 with the accompanying model API rename (Content→ContentBlock) in src/tools/mod.rs; test and fmt CI are green, so the static call sites compile against the new API. No defects found.
- the pull request title was withheld by the untrusted-input screen (injection) — the reviewer did not read it, and developerz.ai will not auto-merge this pull request until a new review of it (the next push, or an
@developerz-ai reviewcomment) reads that text as clean - 1 noise file(s) auto-skipped (lockfiles/generated/vendored — re-include with path_filters)
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/glm-5.3-flash on box sebastian-1 — 24.2k in / 237 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
There was a problem hiding this comment.
Review summary — 2 file(s), 0 finding(s).
Bumps rmcp 1.7→2.2 with the API renames the release requires (Content→ContentBlock); type-checked code is minimal and fmt/test CI is green. No defects found.
- the pull request title was withheld by the untrusted-input screen (injection) — the reviewer did not read it, and developerz.ai will not auto-merge this pull request until a new review of it (the next push, or an
@developerz-ai reviewcomment) reads that text as clean - 1 noise file(s) auto-skipped (lockfiles/generated/vendored — re-include with path_filters)
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/glm-5.3-flash on box hv-dedicated-dev-din — 24.2k in / 301 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
There was a problem hiding this comment.
Review summary — 2 file(s), 0 finding(s).
Dependabot bump of rmcp 1.8→2.2 plus the mechanical API rename it forces (Content→ContentBlock in src/tools/mod.rs). CI (fmt + test/clippy) is green, so the renamed call sites compile against the new model API; no defects found.
- the pull request title was withheld by the untrusted-input screen (injection) — the reviewer did not read it, and developerz.ai will not auto-merge this pull request until a new review of it (the next push, or an
@developerz-ai reviewcomment) reads that text as clean - 1 noise file(s) auto-skipped (lockfiles/generated/vendored — re-include with path_filters)
- test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against
🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/glm-5.3-flash on box hv-dedicated-dev-din — 24.2k in / 171 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).
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)