chore: bump version to 1.30.0

[felixweinberger]

Version bump for the next v1.x release. Since 1.29.0: SSE keep-alive comment frames from the Streamable HTTP server transport (#2538) and the keep-alive timer lifecycle fix on reconnect (#2547), plus the @hono/node-server range widened past GHSA-frvp-7c67-39w9 (#2549). Release flow after merge: publish a GitHub Release tagged v1.30.0 targeting the v1.x branch.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3ed5ff8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@modelcontextprotocol/sdk@2563

commit: 3ed5ff8

[claude]

LGTM — mechanical version bump from 1.29.0 to 1.30.0.

What was reviewed: the version fields in package.json and package-lock.json (both root and packages[""] entries) — all three are updated consistently to 1.30.0, with no other changes in the diff. The changeset-bot warning is expected, since v1.x releases in this repo are cut via manual version bumps rather than changesets.

Extended reasoning...

Overview

This PR changes exactly two files: package.json and package-lock.json, bumping the package version from 1.29.0 to 1.30.0 in all three places it appears (package.json version, lockfile root version, and the lockfile packages[""] entry). No dependencies, scripts, exports, or any other fields are modified.

Security risks

None. The diff contains only version-string changes; no dependency versions or ranges change, so there is no supply-chain or dependency-resolution impact.

Level of scrutiny

Minimal scrutiny is appropriate. This is a routine pre-release chore PR following the established v1.x release pattern (the previous 1.29.0 bump followed the same shape). The only things to verify are internal consistency between package.json and the lockfile (they match) and that the new version is the expected next minor (1.30.0 follows 1.29.0, consistent with the changes since 1.29.0 listed in the description: #2538, #2547, #2549).

Other factors

The bug hunting system found no issues, and there are no outstanding reviewer comments. The changeset-bot "No Changeset found" notice is informational and expected for this repo's release flow, which publishes via a GitHub Release tag on the v1.x branch after merge rather than via changesets.