Update @modelcontextprotocol/sdk & bump version to 0.16.2 #645
Conversation
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
🎭 Playwright E2E Test Results✅ 12 passed Details12 tests across 1 suite 📊 View Detailed HTML Report (download artifacts) |
felixweinberger
force-pushed
the
fweinberger/update-ts-sdk
branch
from
c9c2dcb to
92217bd
Compare
ihrpr
previously approved these changes
Jul 25, 2025
felixweinberger
force-pushed
the
fweinberger/update-ts-sdk
branch
from
ef28b9d to
a00432b
Compare
felixweinberger
changed the title
felixweinberger
force-pushed
the
fweinberger/update-ts-sdk
branch
from
08bb9c7 to
a00432b
Compare
felixweinberger
force-pushed
the
fweinberger/update-ts-sdk
branch
from
a00432b to
939a7da
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation and Context
Updates the
@modelcontextprotocol/sdk dependencyfrom various versions (1.13.1 and 1.14.0) to the latest release 1.17.0 across all workspaces.How Has This Been Tested?
npm install,npm run build,npm run start+ smoke test with a build + run everything server:Breaking Changes
None.
Types of changes
Checklist
Additional context