Repository navigation
chore: version packages - #82
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 1, 2026 16:54
136dd46 to
805cd6c
Compare
|
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
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.14.0
Minor Changes
126272e: Four new components:
Kbd,ButtonGroup,EmptyandInputGroup.These are the first components added since the library finished wrapping every
one of Bits UI's 41 primitives, so all four are hand-built. They were chosen by
diffing the catalog against shadcn-svelte: each one is a gap people currently fill
with a hand-rolled div, and none needs a new dependency.
Kbd— a keycap.labelis the part that matters:⌘,⇧and⌥arepunctuation to a screen reader, and some voices skip them entirely, so a shortcut
rendered as glyphs alone can be announced as nothing at all. With a label the
glyph is hidden from the accessibility tree and the word is announced instead.
The library shipped
Command, a command palette, with no way to draw the shortcutit advertises.
ButtonGroup— attaches independent buttons into one control, collapsing thedoubled border between them and lifting whichever has focus so its ring is never
clipped by a neighbour.
labelorlabelledbyis required: it rendersrole="group", and a role without a name tells a screen reader there is aboundary here and then cannot say what for. Use
Toolbarwhen the whole barshould be one tab stop, and
ToggleGroupwhen the buttons carry a value.Empty— the state a list, table or result set is in with nothing to show.Three defaults, each usually got wrong:
Mediais alwaysaria-hiddenbecausethe icon restates the title;
Titlerenders a<p>rather than a heading, so anempty state inside a card cannot inject "No results" into the document outline;
and
announceis opt-in, for the case that actually needs it — results replacedby emptiness after a search, which is a change the user caused and cannot see.
InputGroup— anInputwith prefix and suffix addons, drawn as one control.The group owns the border and the
:focus-withinring and the input owns neither,which is what makes an addon read as part of the field instead of a box beside it.
Addonisaria-hiddenby default and cannot be the label: a$is a hint forthe eye, and the meaning belongs in the input's accessible name.
Also in this release, both found by tightening a guard rather than by reading code:
apps/example's coverage guard accepted a namespace member as proof of atop-level export, so
\bEmpty\bmatchedCommand.Empty. With that fixed itreported the standalone
Calendaras never rendered — true for months, and nowrendered on the booking screen. A calendar inside a picker is a different mount.
Empty.Rootis not a live region by default was measuring itsown fixture's default. Flipping the component default to
trueleft it green.Caught by mutation, and the fixture now renders the prop genuinely absent.
example@0.0.7
Patch Changes