Conversation
This branch has not been deployed
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
1 participant
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.
Motivation
Deploy the Rstack CLI documentation through Zephyr, following the Rsbuild website setup, with main builds and stable-release production promotion.
Changes
Add the Zephyr Rspress plugin and site org config. Deploy main to Zephyr with the CI token; after a successful
latestnpm release, deploy the exact released source commit to production.Validation:
pnpm build,pnpm --filter rstack build:native, andpnpm checkpassed. The website compiled, but local Zephyr Build ID creation lacked access to the new site identity. The full test run had one docs-restart timeout under parallel load; its focused rerun passed. Pre-commit autoreview was clean. CI requires repository secretZE_CI_TOKENand Zephyr access forrstack-website.rstack-cli.rstack.