Repository navigation
chore(deps): upgrade the MCP TypeScript SDK Node.js adapter to 2.1.2 #5228
Description
A new MCP TypeScript SDK Node.js adapter release is out. What is installed on v2/main is behind what npm publishes.
| Package | Where | Declared | Installed on v2/main |
Latest | Behind |
|---|---|---|---|---|---|
@modelcontextprotocol/node |
src/everything |
^2.1.1 | 2.1.1 | 2.1.2 | yes |
Release notes: https://github.com/modelcontextprotocol/typescript-sdk/releases
Filed by the nightly SDK watch (#4874), one of this repo's issue-filing sweeps. None of them opens a PR: a bot-authored PR has no Closes #N and no board card. A maintainer picks this up and opens a normal PR against v2/main.
Upgrade checklist
- No manifest edit needed: every declared range already admits 2.1.2, so this is a lockfile refresh.
-
npm installat the root, and commit the refreshedpackage-lock.json. -
npm run format, thennpm run local:gate. - Exercise the servers with a client (the
client-smokeskill) if the release changes behavior they rely on.
An automated review of what changed upstream, and which parts of these servers it touches, is posted as a comment below.
A later run will not refile this issue. A further release files its own issue and leaves a supersession note here.
Activity