Deploy the demo automatically for GitHub Releases - #235
Merged
Conversation
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.
Problem
The public demo is served from a legacy
gh-pagesbranch whose latest deployment is from 2019. Publishing a package and GitHub Release does not currently refresh the demo.Change
pages-build/on Node.js 24 using the public npm registry.AGENTS.md.After merge, the repository Pages source will be switched from the legacy branch to GitHub Actions before creating the
v3.2.5GitHub Release.Verification
npm run docproducedpages-build/index.htmland the expected assets.npm run verifypassed with 42 tests, lint, library/demo/SSR builds, hydration, export, and package-content checks.https://registry.npmjs.org/.The first end-to-end deployment will be the
v3.2.5Release event.