GV

GeezerVison

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

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

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

Conversation

@maxisbey

@maxisbey maxisbey commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

The pre-release pin-flip for v2.0.0rc2, following the RELEASE.md pre-release step: the README and get-started docs pinned 2.0.0rc1; they now pin 2.0.0rc2 so the tagged commit's README (the PyPI long description) names the version being released. Merges last before the v2.0.0rc2 tag.

How Has This Been Tested?

Docs-only. A tree-wide git grep 2.0.0rc1 leaves only the true "since 2.0.0rc1" provenance note in the What's new page (that change shipped in rc1); 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
@maxisbey
Point pre-release install pins at 2.0.0rc2
5e6cba8 
The README and get-started docs pinned 2.0.0rc1. Ahead of the 2.0.0rc2 tag
they now pin 2.0.0rc2, so the tagged commit's README (the PyPI long
description) names the version being released.

No-Verification-Needed: doc-only pin flip
@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

📚 Documentation preview
Preview https://pr-3202.mcp-python-docs.pages.dev
Deployment https://b311bdd5.mcp-python-docs.pages.dev
Commit 5e6cba8
Triggered by @maxisbey
Updated 2026-07-28 10:28:26 UTC
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
cubic-dev-ai[bot]
cubic-dev-ai Bot reviewed Jul 28, 2026
View reviewed changes

@cubic-dev-ai 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.

No issues found across 4 files

Re-trigger cubic

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
claude[bot]
claude Bot reviewed Jul 28, 2026
View reviewed changes

@claude 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 — mechanical docs-only pin flip from 2.0.0rc1 to 2.0.0rc2 per the RELEASE.md pre-release step.

What was reviewed

  • All four changed files (README, installation, real-host, index) — every install/one-off-command pin flipped consistently to 2.0.0rc2, no other content changed.
  • Tree-wide grep for 2.0.0rc1 — the only remaining hit is the intentional "since 2.0.0rc1" provenance note in docs/whats-new.md, as the PR description states.
Extended reasoning...

Overview

This PR touches only four Markdown files (README.md, docs/index.md, docs/get-started/installation.md, docs/get-started/real-host.md), replacing every 2.0.0rc1 install pin with 2.0.0rc2. It is the standard pre-release pin-flip described in the PR body, meant to merge last before the v2.0.0rc2 tag so the tagged README (PyPI long description) names the version being released.

Security risks

None. No code, configuration, dependency, or CI changes — the diff is purely version strings inside documentation prose and code blocks.

Level of scrutiny

Low. This is a mechanical find-and-replace of a version string in docs. The main correctness questions are (a) whether every pin was flipped and (b) whether anything unrelated was touched. I verified both: a tree-wide grep shows the only surviving 2.0.0rc1 reference is the provenance note in docs/whats-new.md:200 (which correctly records when a feature shipped and should not be bumped), and the diff contains nothing but the pin substitutions.

Other factors

The bug hunting system found no issues, and the PR timeline has no prior reviews or unresolved comments. CI runs the readme-snippets and docs build checks, which cover these files. The change follows the same pattern as the previous rc1 pin-flip commit already on main.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@maxisbey

maxisbey commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

Closing: skipping rc2 and going straight to v2.0.0. The stable pin flip is #3178.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@maxisbey maxisbey closed this Jul 28, 2026
@maxisbey
maxisbey deleted the rc2-pins branch July 28, 2026 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cubic-dev-ai cubic-dev-ai[bot] cubic-dev-ai[bot] left review comments
@claude 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

@maxisbey
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.