Conversation
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
📚 Documentation preview
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 indocs/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.
|
Closing: skipping rc2 and going straight to v2.0.0. The stable pin flip is #3178. |
1 participant
The pre-release pin-flip for
v2.0.0rc2, following the RELEASE.md pre-release step: the README and get-started docs pinned2.0.0rc1; they now pin2.0.0rc2so the tagged commit's README (the PyPI long description) names the version being released. Merges last before thev2.0.0rc2tag.How Has This Been Tested?
Docs-only. A tree-wide
git grep 2.0.0rc1leaves 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
Checklist
AI disclosure
AI assistance was used to make this change; I reviewed the result and take responsibility for it.
AI Disclaimer