Repository navigation
chore: version packages - #80
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
sve-ui@0.13.2
Patch Changes
579a7a0: Documentation only: the README now lists every component the package exports.
No code changed. This is a release because the README is the npm page, and
npm only re-renders it when a version is published — so the fix reaches nobody
until it ships.
What it was: the README listed 18 of 61 exports and described a sixty-component
library as sixteen.
Table,Toast,Sidebar,Combobox,Command,Select,Tabs,Field,Busyand the entire date family — 43 components — were notnamed anywhere in the file. Anyone evaluating the package from npm was reading a
catalog missing three quarters of its contents.
All 60 are now listed, grouped the way the documentation site groups them, with
.*marking the namespace compositions so the single-versus-namespace importsplit is answerable without leaving the page.
scripts/check-readme-coverage.mjsnow fails the build when an export is missingfrom that table, and separately when the stated count disagrees with the exports.
The registry, the docs pages and the agent skill were already guarded; the one
surface a person actually lands on was not, which is exactly why it rotted
unnoticed.
example@0.0.6
Patch Changes