Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository:modelcontextprotocol/typescript-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:main
Choose a base ref
...
head repository:modelcontextprotocol/typescript-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:release/1.23.1
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 5 files changed
  • 3 contributors

Commits on Dec 4, 2025

  1. fix: disable priming events to fix backwards compatibility

    Priming events (SEP-1699) have empty SSE data which clients in the 1.23.x line cannot handle - they crash trying to JSON.parse(""). This patch disables priming events entirely to prevent breaking existing clients. Priming events will be re-enabled in 1.24.x with proper protocol version gating to only send them to clients that can handle empty SSE data.
    @felixweinberger
    felixweinberger committed Dec 4, 2025
    Configuration menu
    Copy the full SHA
    05c26b3View commit details
    Browse the repository at this point in the history

  2. chore: bump version to 1.23.1

    @felixweinberger
    felixweinberger committed Dec 4, 2025
    Configuration menu
    Copy the full SHA
    e98eeceView commit details
    Browse the repository at this point in the history

  3. fix: use versioned npm tag for non-main branch releases

    When publishing from maintenance branches (e.g., patch-1), use a major.minor tag like "v1.23" instead of defaulting to "latest". This prevents old patches from becoming the latest version on npm. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
    @pcarleton@claude
    pcarleton and claude committed Dec 4, 2025
    Configuration menu
    Copy the full SHA
    0224934View commit details
    Browse the repository at this point in the history

  4. fix: use release-X.Y tag format to avoid semver range conflict

    npm rejects tags like "v1.23" because they look like semver ranges. Use "release-1.23" format instead. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
    @pcarleton@claude
    pcarleton and claude committed Dec 4, 2025
    Configuration menu
    Copy the full SHA
    bd3c461View commit details
    Browse the repository at this point in the history
Loading