Point pre-release install pins at 2.0.0rc2
Closed
MA
3mo ago+15+15+01234567890123456789-15-15-01234567890123456789
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.