Prepare WeBaseUI 1.0 RC - #8
Merged
Merged
Conversation
xuewill
marked this pull request as ready for review
August 17, 2026 23:40
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.
What changed
Why
This completes the repository maturity roadmap needed to prepare the packages for a 1.0 release-candidate cycle. It turns previously implicit component behavior and release expectations into tested contracts and repeatable automation.
Impact
@webaseui/coreand@webaseui/sveltereceive minor-version changes through the included changesetsValidation
npm run check(76 unit tests; 99.61% statements, 99.09% branches, 100% functions and lines; all typechecks and policy gates passed)npm run check:consumer(minimum and current supported Svelte/TypeScript toolchains)npm run test:browser(84/84 across Chromium, Firefox, and WebKit)npm run test:visual(47/47 on macOS Chromium baselines)npm run check:changesetnpm audit --audit-level=high(0 vulnerabilities)git diff --checkRemaining RC sign-off
main, verify thenextchannel publish and npm provenance attestations