[claude]

Requested by Felix Weinberger · Slack thread

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7bc936c

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@3089

commit: 7bc936c

[claude]

I reviewed this PR and found no bugs; because it cuts a release version and both files fall under the repo-wide CODEOWNERS rule, a human look from an owner is still worthwhile.

What was reviewed:

• The diff is three lines: version goes from 1.32.1 to 1.32.2 in package.json and in the two matching fields of package-lock.json (top level and packages[""]); all three agree.
• No dependency ranges, resolved packages or integrity hashes change in the lockfile.
• Searched the repo for a leftover 1.32.1 string outside the lockfile and found none, so no other version reference is out of step.
• .github/workflows/main.yml publishes to npm on a published GitHub release, not on merge, so merging this does not publish by itself.

Extended reasoning...

The change touches only package.json and package-lock.json, bumping the package version from 1.32.1 to 1.32.2 in three places with no dependency, source, test or docs changes. It touches no security-sensitive surface (no auth, injection or data-exposure paths). The bug hunt ran dry with no findings and the timeline shows no open objections. The deciding fact for defer over approve is that .github/CODEOWNERS has a catch-all * rule assigning every path, including these two files, to the typescript-sdk team, and a release version number is a decision an owner should confirm.