Skip to content

Conversation

@felixweinberger
Copy link
Contributor

@felixweinberger felixweinberger commented Dec 2, 2025

tsia

@felixweinberger felixweinberger requested a review from a team as a code owner December 2, 2025 13:22
@felixweinberger felixweinberger enabled auto-merge (squash) December 2, 2025 13:22
@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 2, 2025

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/sdk@1215

commit: c01ab18

@felixweinberger felixweinberger enabled auto-merge (squash) December 2, 2025 13:23
@felixweinberger felixweinberger merged commit 356b7e6 into main Dec 2, 2025
10 checks passed
@felixweinberger felixweinberger deleted the fweinberger/1.24.0 branch December 2, 2025 13:40
@davidmcwherter
Copy link

davidmcwherter commented Dec 6, 2025

@felixweinberger I'm going to point out that this PR seems to have made a backward-incompatible change to this library (changing protocol version) but did NOT change the major version number of this library. As a result we just witnessed several "at least this major version" npm dependency statements end up creating API-breaking changes.

In particular, gemini-cli was depending on 1.23^ and suddenly, for many nightly builds, changed their API protocolVersion which causes server/client version agreement failure. Seems like protocolVersion changes should have forced a 2.0.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants