docs: clarify v2 beta installation guidance#375
Merged
Conversation
wadakatu
marked this pull request as ready for review
July 17, 2026 08:12
wadakatu
force-pushed
the
docs/beta-install-guidance
branch
from
July 23, 2026 06:48
41bd03e to
d101eaa
Compare
wadakatu
force-pushed
the
docs/beta-install-guidance
branch
from
July 23, 2026 06:53
e027b8a to
e79ffe8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
^2.0@betastability opt-in across README, quickstarts, and example READMEsmainafter the beta.4 and documentation-site updatesWhy
Gesso 2 is currently published as
v2.0.0-beta.4. An unqualified install command can read as a stable recommendation even though downstream validation is still part of the beta process. The documentation should make the release status and adoption boundary explicit.The policy test prevents the beta warning and stability flag from remaining during stable promotion. It reads
release-please-config.jsonrather than the release manifest so the normal promotion PR can update the release mode and documentation together; otherwise the bot-managed stable release PR would be the first place the manifest becomes stable and would fail its own CI.Validation
studio-design/gesso:^2.0@betaselectedv2.0.0-beta.4php84 vendor/bin/phpunit tests/Unit/Build/DocumentationInstallPolicyTest.php— 1 test, 38 assertionsnpm run docs:buildnpm run docs:verify-accessibilitynpm run docs:verify-basenpm run docs:verify-tombonpm run docs:verify-versiongit diff --checkローカル実機確認
docs/.vitepress/dist/quickstarts/core.html/ Chrome DevTools MCPPre-release evaluation onlyとcomposer require --dev "studio-design/gesso:^2.0@beta"が読み上げツリーと画面の両方に表示され、PCではコマンドにoverflowなし、モバイルではコードブロック内だけスクロールしページ全体の横overflowなしfile://で確認。CSSは読み込み済み。module scriptとローカルfontはブラウザーのfile://CORS制約で未読込/private/tmp/gesso-pr375-beta4-desktop.png、/private/tmp/gesso-pr375-beta4-mobile.png