Repository navigation
chore(deps-dev): bump @modelcontextprotocol/client from 2.0.0 to 2.2.0 in /packages/agents #2536
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -46,7 +46,7 @@ | |
| "@earendil-works/pi-ai": "^1.0.0", | ||
| "@earendil-works/pi-durable": "^1.0.0", | ||
| "@earendil-works/pi-tui": "1.0.0", | ||
| "@modelcontextprotocol/client": "2.2.0", | ||
| "@modelcontextprotocol/conformance-v2": "npm:@modelcontextprotocol/conformance@0.2.0-alpha.10", | ||
| "@modelcontextprotocol/sdk": "1.30.0", | ||
| "@modelcontextprotocol/server": "2.0.0", | ||
|
|
@@ -73,7 +73,7 @@ | |
| "@cloudflare/codemode": ">=0.5.0", | ||
| "@earendil-works/pi-ai": "^1.0.0", | ||
| "@earendil-works/pi-durable": "^1.0.0", | ||
| "@modelcontextprotocol/client": "2.2.0", | ||
|
Contributor
There was a problem hiding this comment. 🔍 MCP example and guide still pin 2.0.0 The Next.js example and installation guide specify 2.0.0, which the new exact peer requirement excludes. Align them with the supported client version. Was this helpful? React with 👍 or 👎 to provide feedback. |
||
| "@modelcontextprotocol/sdk": "1.30.0", | ||
| "@modelcontextprotocol/server": "2.0.0", | ||
| "@opencode/plugin": "^2.0.24", | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Frozen installs reject the client upgrade
With
@modelcontextprotocol/clientset to 2.2.0,pnpm install --frozen-lockfilerejects the unchanged 2.0.0 lockfile specifier. The CI install fails before builds and tests run.Learn more
The workspace lockfile records a specifier for each dependency of each importer. The agents importer still records
@modelcontextprotocol/clientas2.0.0despite this manifest requiring2.2.0. The CI install freezes the lockfile and rejects mismatched importers, stopping the PR before build and test.Example: On this branch, the agents importer asks for
2.2.0, while the lockfile asks for2.0.0; a frozen pnpm install exits with an outdated lockfile error rather than installing the new client.Recommended fix: Regenerate
pnpm-lock.yamlusingpnpm installfrom the workspace root and commit it alongside the manifest update. Verifypnpm install --frozen-lockfilesucceeds.Was this helpful? React with 👍 or 👎 to provide feedback.