v1.0.0: stamp Python CalVer versions for 2026.10.10 (release branch)

[cliffhall]

Closes #5080

Targets the one-time release branch v2/release/1.0.0 (SDK 1.x, decided on #5080).

Step 2c of the v1.0.0 release on the release branch: the Prepare Python Release stamp, run by hand with the same script (prepare-python-release.yml is not on the default branch yet).

Description

node scripts/prepare-python-release.mjs on v2/release/1.0.0 at c38bd86f (after #5086, #5087, #5088):

mcp-server-fetch: 0.6.3 -> 2026.10.10
mcp-server-git: 0.6.2 -> 2026.10.10
mcp-server-time: 0.6.2 -> 2026.10.10

Each server's pyproject.toml version and its own uv.lock entry: six lines, nothing else. Same versions as #5084 on v2/main, so the post-release reconciliation of v2/main has nothing to resolve here.

Server Details

• Server: fetch, git, time
• Changes to: version metadata only

Motivation and Context

#4968 scope item 3, on the SDK 1.x release line. PyPI's latest is 2026.8.18 for all three; the 0.6.x in pyproject.toml was never published (the old pipeline stamped at publish time).

How Has This Been Tested?

$ git diff --numstat origin/v2/release/1.0.0      -> 1/1 in each pyproject.toml and uv.lock
$ curl -s -o /dev/null -w '%{http_code}' https://pypi.org/pypi/mcp-server-<name>/2026.10.10/json
404  (fetch, git, time: each will publish)
$ npm run local:gate; echo EXIT=$?
EXIT=0

Breaking Changes

None from this PR.

Types of changes

• Version metadata only

Checklist

• I have read the MCP Protocol Documentation (not applicable)
• My changes follow MCP security best practices (not applicable)
• I have updated the server's README accordingly (not applicable)
• I have added a changeset (not applicable: Python servers)
• I have tested this with an LLM client (not applicable: version metadata only)
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling (not applicable)
• I have documented all environment variables and configuration options (not applicable)

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1f8b6eb

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

[Copilot]

🟢 Approval recommended

All three manifest versions and lockfile entries are consistently stamped with the intended release CalVer.

0 open findings

What changed in this PR

Stamps the three Python servers with the 2026.10.10 CalVer for the v1.0.0 release branch.

Changes:

• Updates each package version.
• Synchronizes each corresponding uv.lock.

File	Description
src/​fetch/​pyproject.toml	Updates fetch to 2026.10.10.
src/​fetch/​uv.lock	Synchronizes fetch lock metadata.
src/​git/​pyproject.toml	Updates git to 2026.10.10.
src/​git/​uv.lock	Synchronizes git lock metadata.
src/​time/​pyproject.toml	Updates time to 2026.10.10.
src/​time/​uv.lock	Synchronizes time lock metadata.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[cliffhall]

Copilot round 1: clean (0 findings, approval recommended). CI 30/30 green. Loop ends on the first clean round. Ready for a maintainer merge; it is the last preparation PR on v2/release/1.0.0 (#5080).