Repository navigation
Add a React portal example and first-alpha release checks - #7
Merged
Merged
Conversation
added 4 commits
October 28, 2026 21:11
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.
The release candidate previously had only a vanilla package consumer. Add a React 19.3.1 portal example and verify the same tarball in two separate clean consumers.
The example uses development StrictMode and covers a corrected dialog after remount, wrong initial focus, and lost return focus. A separate process must fail with exit 1. Standard HTML/JUnit reports and the original attachment retain the first mismatch and dependent
not_runobservations. React remains an example-only dependency.Package preparation resolves the local archive and registry metadata into a temporary lockfile without installing node_modules. A separate empty consumer then installs with
--offline --frozen-lockfile. This preserves required esbuild platform packages and pnpm policy checks. CI verifies package consumers before running the unchanged regression suite.Add a report-reading guide, draft first-alpha notes, a release checklist, a focused bug-report template, SHA-256 output, and CI uploads of the tested archive and reports. Runtime code, ruleset, schema, and accepted 45-round evidence are unchanged. The candidate remains unpublished
0.1.0-alpha.5.Validation on macOS / Node 24.22.1 / Playwright 1.64.1:
pnpm check: strict types, 30 unit tests, 48 guard subprocess cases, and 153 browser tests passed.3d2068502b8241bbc78d3161c763e7b24026b820; both platform artifacts contain the tested archive, checksums and consumer reports.The original 100-round criterion remains unmet; this prepares the accepted alpha checkpoint, not full 0.1.0 acceptance or publication.