chore(changesets): only bump peer dependents when out of range

[claude]

Requested by Felix Weinberger · Slack thread

Problem: with the currently pending changesets, changeset version bumps @modelcontextprotocol/node, @modelcontextprotocol/express, @modelcontextprotocol/hono and @modelcontextprotocol/fastify from 2.0.0 to 3.0.0 (see #2808). The DPoP changeset is minor on client + core, which sit in a fixed group with server, so server goes to 2.1.0; changesets by default treats every peer dependent of a bumped package as needing a major, even though the adapters' workspace:^ peer range still covers 2.1.0.

Fix: set onlyUpdatePeerDependentsWhenOutOfRange: true under ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH in .changeset/config.json (as a top-level key changesets silently ignores it). Peer dependents then only bump when the new version leaves their declared peer range; workspace:^ stays in range for minors and patches, so the adapters take their own patch bump from request-body-size-limit.md instead of a spurious major.

Dry runs of pnpm exec changeset version against main 603217008 (12 pending changesets):

Package	Before	After
@modelcontextprotocol/core	2.0.0 → 2.1.0	2.0.0 → 2.1.0
@modelcontextprotocol/client	2.0.0 → 2.1.0	2.0.0 → 2.1.0
@modelcontextprotocol/server	2.0.0 → 2.1.0	2.0.0 → 2.1.0
@modelcontextprotocol/server-legacy	2.0.0 → 2.1.0	2.0.0 → 2.1.0
@modelcontextprotocol/codemod	2.0.0 → 2.1.0	2.0.0 → 2.1.0
@modelcontextprotocol/core-internal	2.0.0 → 2.0.1	2.0.0 → 2.0.1
@modelcontextprotocol/node	2.0.0 → 3.0.0	2.0.0 → 2.1.0
@modelcontextprotocol/express	2.0.0 → 3.0.0	2.0.0 → 2.0.1
@modelcontextprotocol/hono	2.0.0 → 3.0.0	2.0.0 → 2.0.1
@modelcontextprotocol/fastify	2.0.0 → 3.0.0	unchanged (no changeset touches it; not published)

@modelcontextprotocol/node lands on 2.1.0 rather than 2.0.1 because #1624 (scope-challenge-server.md) added its own minor changeset for node, so it takes a minor regardless of this option.

pnpm pack of the versioned node, express and hono packages publishes their @modelcontextprotocol/server peer range as ^2.1.0, which is the existing workspace:^ behaviour and is unaffected by this option.

VERSIONING.md already documents that the adapters bump only when their @modelcontextprotocol/server peer range has to move (or for their own changes), so no doc change; no changeset because this is config-only.

🤖 Generated with Claude Code

https://claude.ai/code/session_012VRbFCp41otcScXE1YY3es

[changeset-bot]

⚠️ No Changeset found

Latest commit: 264ff58

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@2819

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2819

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2819

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@2819

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2819

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@2819

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2819

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@2819

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@2819

commit: 264ff58

[claude]

Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.