GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — Point pre-release install pins at 2.0.0rc1 by maxisbey · Pull Request #3186 · modelcontextprotocol/python-sdk

Conversation

maxisbey commented Jul 27, 2026

Copy link

Copy Markdown

Contributor

The pre-release pin-flip for v2.0.0rc1, following the RELEASE.md pre-release step: the README and get-started docs pinned 2.0.0b1 and described v2 as a beta; they now pin 2.0.0rc1 and describe it as a release candidate, so the tagged commit's README (the PyPI long description) names the version being released. This should merge last before the v2.0.0rc1 tag.

Motivation and Context

Same shape as the b1 pin flip. Also fixes a stale token: the What's new page said the serverInfo _meta change shipped "since 2.0.0b3", a release that was never cut; that change first ships in this rc.

How Has This Been Tested?

Docs-only. git grep 2.0.0b1 in README and docs is now empty; the readme-snippets and docs build checks run in CI.

Breaking Changes

None.

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

AI disclosure

AI assistance was used to make this change; I reviewed the result and take responsibility for it.

_{AI Disclaimer}

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          Point pre-release install pins at 2.0.0rc1

8f24f09

The README and get-started docs pinned 2.0.0b1 and described v2 as a beta.
Ahead of the 2.0.0rc1 tag they now pin 2.0.0rc1 and describe v2 as a release
candidate, so the tagged commit's README (the PyPI long description) names
the version being released. The What's new page's serverInfo `_meta` note
also drops its reference to a 2.0.0b3 release that was never cut: that
change first ships in 2.0.0rc1.

No-Verification-Needed: doc-only pin flip

github-actions Bot commented Jul 27, 2026

Copy link

Copy Markdown

Contributor

📚 Documentation preview


Preview	https://pr-3186.mcp-python-docs.pages.dev
Deployment	https://037435d5.mcp-python-docs.pages.dev
Commit	`8f24f09`
Triggered by	@maxisbey
Updated	2026-07-27 13:16:47 UTC

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

cubic-dev-ai Bot reviewed

Jul 27, 2026

View reviewed changes

cubic-dev-ai Bot left a comment

Copy link

Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 5 files

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/get-started/real-host.md">

<violation number="1" location="docs/get-started/real-host.md:26">
P2: Running these commands from a directory containing a project can let `uv` update its lockfile. Show `--frozen` in every documented launch command, matching the repository’s `uv` policy and the generated Claude Desktop entry.</violation>
</file>

_{Reply with feedback, questions, or to request a fix.

Re-trigger cubic}

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

docs/get-started/real-host.md


		```bash
		uv run --with "mcp[cli]==2.0.0b1" mcp run /absolute/path/to/server.py
		uv run --with "mcp[cli]==2.0.0rc1" mcp run /absolute/path/to/server.py

cubic-dev-ai Bot Jul 27, 2026

Copy link

Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Running these commands from a directory containing a project can let uv update its lockfile. Show --frozen in every documented launch command, matching the repository’s uv policy and the generated Claude Desktop entry.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/get-started/real-host.md, line 26:

<comment>Running these commands from a directory containing a project can let `uv` update its lockfile. Show `--frozen` in every documented launch command, matching the repository’s `uv` policy and the generated Claude Desktop entry.</comment>

<file context>
@@ -23,15 +23,15 @@ That is the last line of Python on this page. From here down it is all host conf
 
 ```bash
-uv run --with "mcp[cli]==2.0.0b1" mcp run /absolute/path/to/server.py
+uv run --with "mcp[cli]==2.0.0rc1" mcp run /absolute/path/to/server.py

</file context>


</details>

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

maxisbey merged commit 45f2a88 into main

Jul 27, 2026

39 checks passed

Uh oh!

There was an error while loading. Please reload this page.

maxisbey deleted the rc1-pins branch

July 27, 2026 13:24

claude Bot reviewed

Jul 27, 2026

View reviewed changes

claude Bot left a comment

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — a mechanical docs-only pin flip from 2.0.0b1 to 2.0.0rc1, matching the RELEASE.md pre-release step.

What was reviewed:

All five files: every 2.0.0b1 pin and "beta" wording is consistently updated to 2.0.0rc1 / "release candidate"; a repo-wide grep confirms no stale 2.0.0b1, 2.0.0b3, or "in beta" references remain.
The whats-new.md "since 2.0.0b3" → "since 2.0.0rc1" correction for the serverInfo _meta change matches the PR description's rationale (b3 was never cut).
A candidate concern that whats-new.md credits client.listen to 2.0.0b2 was investigated and ruled out (b2 is a real release).

Extended reasoning...

Overview

This PR touches only README.md and four docs pages (installation, real-host, index, whats-new). Every change is either a version-pin string flip (2.0.0b1 → 2.0.0rc1) or accompanying prose updating "beta" to "release candidate" / "pre-release". One substantive prose fix corrects a stale claim that the serverInfo _meta change shipped in 2.0.0b3 (a release that was never cut) to 2.0.0rc1, which the PR description explains.

Security risks

None. No code, configuration, dependency, or CI changes — purely documentation text. The install commands documented are the same shape as before with only the version string changed.

Level of scrutiny

Low. This is the same pin-flip pattern used for the previous 2.0.0b1 release step per RELEASE.md, is docs-only, and carries no runtime behavior. The main failure modes would be a missed stale pin or an inconsistent version reference; a repo-wide grep confirms no 2.0.0b1, 2.0.0b3, or lingering "in beta" phrasing remains, and the readme-snippets/docs-build CI checks cover formatting.

Other factors

The bug hunting system found no bugs. Its one candidate issue — that whats-new.md credits client.listen to a never-cut 2.0.0b2 — was examined and refuted by verifiers. The PR has no prior reviews or outstanding comments. The author notes it should merge last before the v2.0.0rc1 tag, which is a sequencing concern for the release manager, not a correctness issue in the diff.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Reviewers

cubic-dev-ai[bot]

cubic-dev-ai[bot] left review comments

claude[bot]

claude[bot] left review comments

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.