test: Loosen MCP v2 dependency pins in test apps - #23643
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
size-limit report 📦
|
nicohrubec
approved these changes
Aug 26, 2026
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.
What
The MCP v2 test dependencies (
@modelcontextprotocol/client,@modelcontextprotocol/node,@modelcontextprotocol/server) now use^2.0.0instead of an exact2.0.0, across the node integration tests and thenode-express-mcp-v2andcloudflare-mcpe2e apps.cloudflare-mcp-agentkeeps its exact@modelcontextprotocol/sdkpin, becauseagentsdepends on that specific version.Why
The exact pins were copied from app to app rather than chosen, and nothing here needs a frozen version. Follow-up to #23569.