chore: exit changesets prerelease mode

[felixweinberger]

Exits changesets pre-release mode so the next Version Packages PR computes stable versions (2.0.0) for the fixed group instead of beta prereleases.

Merge order: after #2564 lands, merge this, then merge the regenerated Version Packages PR (#2555) and approve the publish. Stable versions publish to the latest dist-tag automatically.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 614c315

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

Name	Type
@modelcontextprotocol/client	Patch
@modelcontextprotocol/codemod	Patch
@modelcontextprotocol/core-internal	Patch
@modelcontextprotocol/core	Patch
@modelcontextprotocol/express	Patch
@modelcontextprotocol/fastify	Patch
@modelcontextprotocol/hono	Patch
@modelcontextprotocol/node	Patch
@modelcontextprotocol/server-legacy	Patch
@modelcontextprotocol/server	Patch
@modelcontextprotocol/examples	Patch
@mcp-examples/bearer-auth-web	Patch
@mcp-examples/bearer-auth	Patch
@mcp-examples/caching	Patch
@mcp-examples/cli-client	Patch
@mcp-examples/client-quickstart	Patch
@mcp-examples/custom-methods	Patch
@mcp-examples/custom-version	Patch
@mcp-examples/dual-era	Patch
@mcp-examples/elicitation	Patch
@mcp-examples/extension-capabilities	Patch
@mcp-examples/gateway	Patch
@mcp-examples/hono	Patch
@mcp-examples/json-response	Patch
@mcp-examples/legacy-routing	Patch
@mcp-examples/mrtr	Patch
@mcp-examples/oauth-client-credentials	Patch
@mcp-examples/oauth	Patch
@mcp-examples/parallel-calls	Patch
@mcp-examples/prompts	Patch
@mcp-examples/repl	Patch
@mcp-examples/resources	Patch
@mcp-examples/sampling	Patch
@mcp-examples/schema-validators	Patch
@mcp-examples/scoped-tools	Patch
@mcp-examples/server-quickstart	Patch
@mcp-examples/shared	Patch
@mcp-examples/sse-polling	Patch
@mcp-examples/standalone-get	Patch
@mcp-examples/stateless-legacy	Patch
@mcp-examples/stickynotes	Patch
@mcp-examples/streaming	Patch
@mcp-examples/subscriptions	Patch
@mcp-examples/todos-server	Patch
@mcp-examples/tools	Patch
@modelcontextprotocol/test-conformance	Patch
@modelcontextprotocol/test-e2e	Patch
@modelcontextprotocol/test-helpers	Patch
@modelcontextprotocol/test-integration	Patch

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

@modelcontextprotocol/codemod

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

@modelcontextprotocol/core

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

@modelcontextprotocol/server

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

@modelcontextprotocol/server-legacy

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

@modelcontextprotocol/express

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

@modelcontextprotocol/fastify

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

@modelcontextprotocol/hono

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

@modelcontextprotocol/node

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

commit: 614c315

[claude]

LGTM — mechanical one-line change flipping changesets from prerelease to exit mode.

What was reviewed

• Verified the diff matches exactly what changeset pre exit generates: only mode flips to exit; tag, initialVersions, and the consumed-changesets list are correctly preserved until the next changeset version run consumes and deletes the file.
• Confirmed the changeset-bot "no changeset" warning is expected — a release-mode toggle should not itself bump versions.
• No code, schema, or workflow changes are involved.

Extended reasoning...

Overview

This PR changes a single line in .changeset/pre.json: "mode": "pre" → "mode": "exit". This is the standard output of running changeset pre exit, which tells changesets that the next changeset version run should compute stable versions (2.0.0) for the fixed group instead of beta prereleases, then delete pre.json. The rest of the file (tag, initialVersions, the list of already-consumed changesets) is untouched, which is exactly what the tool preserves.

Security risks

None. No executable code, dependencies, CI workflows, or auth-related files are touched — only release-tooling state.

Level of scrutiny

Low for correctness: the change is mechanical and tool-generated, and there is only one way this file can be wrong (a malformed mode value), which it is not. The consequential part is the release decision — exiting prerelease means the next Version Packages PR will produce stable 2.0.0 versions published to the latest dist-tag. That decision is explicitly the point of the PR, is described in the PR body with the intended merge order (after #2564, before the regenerated #2555), and is gated behind two further human-controlled steps (merging the Version Packages PR and approving the publish). Approval here does not itself trigger a publish.

Other factors

The bug hunting system found no issues, and there is nothing in this diff where a bug could hide. The changeset-bot "No Changeset found" warning is expected and correct for a release-mode toggle. The recurring-catches guidance about verifying CI/publish claims does not apply — no workflow files are modified. Repository main is already at the corresponding commit, consistent with this being a routine, planned release step.