Upgrade rmcp to 3.0.1 - #69
Merged
Merged
Conversation
Signed-off-by: lucarlig <luca.carlig@ibm.com>
Signed-off-by: lucarlig <luca.carlig@ibm.com>
lucarlig
marked this pull request as ready for review
July 30, 2026 10:00
gandhipratik203
approved these changes
Jul 30, 2026
gandhipratik203
left a comment
gandhipratik203
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the upgrade. Accepting the changes as we are moving to the new protocol. LGTM!
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
2 participants
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
rmcpandrmcp-macrosfrom3.0.0-beta.3to stable3.0.1Metaalias toMetaObjectbase640.23 dependencyWhy
rmcp3.0.1 is the latest stable release. It includes fixes for stateless initialize negotiation, missing protocol-header handling, graceful subscription results, and OAuth token refresh against discovered resources. Moving off the beta keeps the dataplane on the supported MCP 2026-07-28 SDK line.Impact
The gateway now builds against the stable RMCP 3.0 API and receives the upstream protocol fixes above. No ContextForge public API or routing contract changes are introduced.
Validation
cargo fmt --all --checkcargo check --workspace --all-targetscargo clippy --locked --workspace --all-targets -- -D warningscargo deny check advisories bans licensescargo shear --check-test-targets --deny-warnings --lockedcargo nextest run --locked --workspace(75 passed)cargo build --locked --workspacecargo bench --locked --workspace --no-run