Point pre-release install pins at 2.0.0b1 - #3039
Conversation
Sorry, something went wrong.
📚 Documentation preview
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM — mechanical docs-only version pin flip (2.0.0a3 → 2.0.0b1) matching RELEASE.md's pre-release step 1.
Extended reasoning...Overview
The PR touches only documentation: README.md, docs/index.md, and docs/installation.md. Every 2.0.0a3 install-pin example becomes 2.0.0b1, and the four "in alpha" phase mentions in the docs become "in beta". A grep of the repo confirms no 2.0.0a3 references or "in alpha" phrasing remain in the docs, so the flip is complete and consistent. No source code, configuration, or build files change; the package version itself comes from the release tag.
Security risks
None. The change is text-only in markdown files — there is no code path, dependency, or configuration affected. The README banner already covers both alpha and beta phases, so no wording there needed updating.
Level of scrutiny
Low. This is exactly the mechanical pre-tag step described in RELEASE.md ("v2 Pre-releases", step 1): update the version examples and phase wording so the tagged commit's README and docs name the version being released. The change matches that instruction precisely and the docs/migration.md "earlier alphas" wording is correctly left as historical.
Other factors
The bug hunting system found no issues, the docs preview deployed cleanly, and the diff is small and self-contained. This fits the criteria for approval without human review.
Sorry, something went wrong.
Pre-tag flip for the first v2 beta, per RELEASE.md ("v2 Pre-releases", step 1):
docs/migration.md's "earlier alphas" wording is historical and stays. No source changes; the package version comes from the tag.
This needs to be in the tagged commit so the published README and docs name the version being released — intended to merge last before the v2.0.0b1 tag.
AI Disclaimer