First semver release: TypeScript servers at 1.0.0 and Python servers at the next CalVer, the frozen legacy-era servers #4968

Follow-up to #4472 and #4873 (agentic software factory tracker #4858, Wave 5). Their PRs (#4927, #4928) merged to v2/main; these are the items left over that only the first release through the new flow can complete.

What this release is

The first semver release of the TypeScript servers, as 1.0.0, together with the next CalVer release of the Python servers, cut from v2/main as it stands now.

It freezes the last and best versions of the legacy-era servers for reference:

• the agentic software factory is in place (Tracker: Agentic software factory (AGENTS.md, skills, quality gates, v2/main release flow) #4858);
• every server clears the 90% per-file coverage gate (Bugs, Coverage, and SDK Wave 1 Part 1: TypeScript servers: extensive unit tests + per-file 90% coverage gate #4854, Bugs, Coverage, and SDK Wave 1 Part 2: Python servers: extensive unit tests + per-file 90% coverage gate #4855);
• the bugs that work found, reported and discovered, are fixed (Bugs, Coverage, and SDK Wave 2: fix the known bugs the Wave 1 suites pin (legacy-era servers) #5004);
• every server runs on the v2 TypeScript and Python SDKs, as a transparent refactor (Spec Refactor Wave 1 Part 1: Migrate TypeScript servers to TS SDK v2 (codemod) #4856, Spec Refactor Wave 1 Part 2: Migrate Python servers to Python SDK v2 #4851).

The legacy-era to modern-era protocol refactor (#4852, #4853) is not part of this release. It ships afterward as 2.0.0, and later milestones carry on as 2.1.0, 2.2.0, and so on.

Scope

1. Release one milestone end to end through the release skill. v2/main → main milestone release flow and release skill #4873's acceptance criterion: release issue, preparation PRs on v2/main, the pure v2/main → main merge PR with its ledger linked, then the published GitHub Release, with release.yml publishing every package.
2. Publish the TypeScript servers at 1.0.0, not 2.0.0. All four package.json files already read 1.0.0, which has never been published, but .changeset/ holds one pending major changeset per server (*-sdk-v2.md, from Spec Refactor Wave 1 Part 1: Migrate TypeScript servers to TS SDK v2 (codemod) #4856) next to their patches. A normal Version Packages PR would consume them and bump all four to 2.0.0. The preparation for this release has to publish 1.0.0 instead. Two ways to do it, to be settled in the preparation PR:
   • (Recommended) Fold the pending changesets into a 1.0.0 CHANGELOG entry for each server and delete them, in one preparation PR. No version changes, so this stays within "a version changes only in a version PR". 1.0.0's changelog then describes everything since 2026.8.31, and 2.0.0 starts from an empty .changeset/ holding only the modern-era work.
   • Skip Version Packages for this release and let release.yml publish the unpublished 1.0.0 as it stands. The pending changesets stay, and the next Version Packages PR turns them into 2.0.0, so 2.0.0's changelog would list SDK v2 changes that actually shipped in 1.0.0.
3. Release the Python servers at the next CalVer, through the Prepare Python Release PR, as the release skill describes.
4. Deprecate the date-stamped npm versions, after 1.0.0 is live. From New release pipeline, Phase 2: semver via changesets (TS), GitHub-Release-triggered publishing #4472's checklist. On all four TypeScript packages, deprecate >=2025.0.0 <2027.0.0 with a pointer to the resumed semver line.
   • Not before the first semver publish. Today latest is 2026.8.31 on all four, so deprecating now would warn every npx user and point them at a version that does not exist yet.
   • Run by a scope maintainer on their own machine (npm deprecate needs an owner login; the release flow's OIDC does not cover it). The check to run first and the exact command are in the release skill, "The first semver release only: deprecate the date-stamped versions".

The PyPI trusted-publisher check from #4472 is not carried over: mcp-server-fetch, mcp-server-git and mcp-server-time last published through release.yml, which confirms the binding.

Acceptance criteria

• The first milestone release has gone through the release skill end to end, and its release issue is closed.
• All four TypeScript packages show 1.0.0 as latest on npm (not 2.0.0), and npm view @modelcontextprotocol/server-<name>@2026.8.31 deprecated prints the deprecation message for each.
• mcp-server-fetch, mcp-server-git and mcp-server-time show the new CalVer as their latest version on PyPI.
• .changeset/ holds no changeset from before this release, so the next Version Packages PR bumps only for the modern-era work (Spec Refactor Wave 2 Part 1: Modern-era TypeScript servers + new features in everything #4852, Spec Refactor Wave 2 Part 2: Modern-era Python servers #4853).