Repository navigation
chore(deps): @modelcontextprotocol/sdk 1.30.0 → 1.32.2 - #10706
Conversation
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
AI review status for this pull request.
|
PR Analysis Report🔎 Preview ·
|
There was a problem hiding this comment.
Approved pending CI: CI has not run on this head yet.
The SDK move is minimal: the lockfile changes only @modelcontextprotocol/sdk (both of its peer variants), the 1.32.2 integrity matches the npm registry, and its dependency list is unchanged from 1.30.0. A before/after run of the docsite's MCP route configuration returned identical handshake, tool-list and tool-call results; the only difference is that a tools/call sent without arguments now names the missing field in its error.
Next step: mark the pull request ready for review so its CI runs, including the docsite build and tests; the Vercel preview build of this head already succeeded.
[Automated review]
Supersedes #7764 (co-authored by dependabot).
Maintainer impact
@modelcontextprotocol/sdk1.30.0.minimumReleaseAge. The docsite's range becomes^1.32.0, as dependabot proposed.fast-uri,joseandqsreleases that were still inside the release-age window. A fresh pnpm 11.10.0 resolution doesn't, and the supply-chain policy check passes.Change
apps/docsite/package.json:@modelcontextprotocol/sdk^1.30.0→^1.32.0.pnpm-lock.yaml: regenerated with pnpm 11.10.0. Only@modelcontextprotocol/sdk(1.30.0 → 1.32.2, both of its peer variants) andmcp-handler's resolved peer move.The docsite is private, so there's no Changeset.
Evidence
pnpm install --lockfile-onlypasses the supply-chain policy check.