Skip to content

An open source design system that's fully customizable and agent ready

TypeScript

chore: version packages for v0.4.7

Cindy Zhang2ce198374b10
diff --git a/.changeset/bottom-sheet-noscrim-edge-tint.md b/.changeset/bottom-sheet-noscrim-edge-tint.md
deleted file mode 100644
index 04f842342e..0000000000
--- a/.changeset/bottom-sheet-noscrim-edge-tint.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] BottomSheet: a non-modal sheet now colours the iOS 26 Safari toolbar strip with its own surface instead of letting the page show through behind the address bar (#5342).
-
-@imdreamrunner
diff --git a/.changeset/bottom-sheet-tap-and-exit.md b/.changeset/bottom-sheet-tap-and-exit.md
deleted file mode 100644
index 9f7195bbec..0000000000
--- a/.changeset/bottom-sheet-tap-and-exit.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] BottomSheet: a tap inside the sheet is a tap, and the sheet leaves on an exit curve (#5326).
-
-Two defects, both of which read as "the sheet closes with no animation" — reported against the touch DateInput picker, which is a Bottom Sheet.
-
-**A tap inside the sheet started a one-pixel drag.** The sheet body carries the pull-to-dismiss handlers, and they promoted to a sheet drag on _any_ downward movement. A finger is never still, so the pixel or two a tap drifts began a drag — and a live drag suppresses the panel's transition, correctly, because a dragged sheet must track the finger rather than lag it. The close that the tap triggered landed inside that window, so the sheet jumped to its closed position with no transition. Tapping the picker's Save button hit this every time; tapping the scrim never did, because the scrim is the dialog itself and arms no gesture. Promotion now needs 8px of travel — the conventional tap slop, well under what a deliberate pull covers in its first frames — in both the pointer and touch paths. The gesture's transition suppression is also scoped to a sheet that is open, so it cannot straddle an exit.
-
-**The exit ran on the entrance's curve.** `--ease-standard` is `cubic-bezier(0.24, 1, 0.4, 1)`, a decelerate curve: it spends its speed immediately and coasts. Right for an entrance, wrong for an exit. Measured on device (iPhone, real Safari), a scrim tap put the sheet half off-screen in 59ms of the 410ms transition and 90% off in 163ms, with the dim gone before it — so the close was over before the eye could follow it. The closing state now carries an accelerating curve of its own, `cubic-bezier(0.3, 0, 0.6, 0.6)`: away from rest, gathering speed, quickest as it leaves the screen, and moving within ~50ms so it reads as one departure rather than a hesitation and a snap. Only the curve changes — the exit keeps `--duration-medium`, the entrance's band, which is what keeps it legible under a theme that scales the motion scale down (neutral's medium is 300ms against the base 410ms).
-
-The scrim leaves with the sheet: while closing, the dim runs `linear` rather than the decelerate token. A fade covers no distance, so front-loading its progress just ends it early — the reasoning the touch date picker's surface swap already carries. `BottomSheetSwitcher` gets the same treatment when its flow closes; a handoff between two sheets is not a close and is unchanged.
-
-@imdreamrunner
diff --git a/.changeset/list-focus-escape-passthrough.md b/.changeset/list-focus-escape-passthrough.md
deleted file mode 100644
index 4d22e1ce9d..0000000000
--- a/.changeset/list-focus-escape-passthrough.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] `useListFocus` no longer swallows Escape when no `onEscape` was supplied. The hook called `preventDefault()` on every Escape — a habit inherited from the arrow keys, which share the handler and need it to suppress page scroll — so a list with nothing to dismiss still marked the key handled, and a surrounding layer that defers to `defaultPrevented` (a focus trap, a native popover) never got its turn. Escape is now consumed only when an `onEscape` is passed. Arrow, Home and End handling is unchanged (#5346).
-
-Behaviour change: `AvatarGroup`, `ButtonGroup`, `Outline`, `Pagination`, `SegmentedControl`, `TabList` and `Toolbar` pass no `onEscape`, so an Escape pressed inside one of them now reaches the surrounding layer and can dismiss it — the point of the fix, but a host that counted on the key stopping there will notice. `NavHeadingMenu` does the same when it renders without a menu close handler. Menus and flyouts that do pass `onEscape` are unaffected. `patch`, not `[breaking]`: the swallowing was never a contract — the hook documented Escape only as "custom callback", and no component advertised consuming the key.
-
-@cixzhang
diff --git a/.changeset/tab-generic-aria-current.md b/.changeset/tab-generic-aria-current.md
deleted file mode 100644
index 5b4c2220d5..0000000000
--- a/.changeset/tab-generic-aria-current.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] TabList: the selected tab now carries `aria-current="true"` — ARIA's generic "current item within a set" — instead of `aria-current="page"`. The strip is a `<nav>` and stays one, but it is used to switch views in place at least as often as it is used to navigate, and on those uses `page` asserted a page change that never happened. Assistive tech announced the selected tab as the _current page_ even when nothing had navigated; it now announces it as the _current item_, which is true either way. A tab given an `href` still renders an anchor and still reads as a link — its current marker is just less specific than it was. No role changes and no new props. (#5347)
-
-@cixzhang
diff --git a/packages/build/CHANGELOG.md b/packages/build/CHANGELOG.md
index 728e3adde4..dec7c9ee23 100644
--- a/packages/build/CHANGELOG.md
+++ b/packages/build/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/build
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/build/package.json b/packages/build/package.json
index 8b060ce961..e62a0b6c82 100644
--- a/packages/build/package.json
+++ b/packages/build/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/build",
- "version": "0.4.6",
+ "version": "0.4.7",
"description": "Build plugins for XDS source builds — babel, PostCSS, and Vite integrations",
"author": "Meta Open Source",
"license": "MIT",
diff --git a/packages/charts/package.json b/packages/charts/package.json
index b42cf8ba67..05adcd8725 100644
--- a/packages/charts/package.json
+++ b/packages/charts/package.json
@@ -58,7 +58,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19.0.0",
"react-dom": ">=19.0.0"
},
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index cee19b4ec2..5f10deacd7 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/cli
+# 0.4.7
+
+---
+
# 0.4.6
#### New Features
diff --git a/packages/cli/package.json b/packages/cli/package.json
index 878002955d..84c1d71c18 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/cli",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "CLI",
"description": "Scaffold projects, browse templates, generate themes, and get agent-ready docs from the command line.",
"author": "Meta Open Source",
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
index c32bbe0f96..bb0314c088 100644
--- a/packages/core/CHANGELOG.md
+++ b/packages/core/CHANGELOG.md
@@ -1,5 +1,31 @@
# @xds/core
+# 0.4.7
+
+#### Fixes
+
+- BottomSheet: a non-modal sheet now colours the iOS 26 Safari toolbar strip with its own surface instead of letting the page show through behind the address bar (#5342).
+- BottomSheet: a tap inside the sheet is a tap, and the sheet leaves on an exit curve (#5326).
+ Two defects, both of which read as "the sheet closes with no animation" — reported against the touch DateInput picker, which is a Bottom Sheet.
+
+ **A tap inside the sheet started a one-pixel drag.** The sheet body carries the pull-to-dismiss handlers, and they promoted to a sheet drag on _any_ downward movement. A finger is never still, so the pixel or two a tap drifts began a drag — and a live drag suppresses the panel's transition, correctly, because a dragged sheet must track the finger rather than lag it. The close that the tap triggered landed inside that window, so the sheet jumped to its closed position with no transition. Tapping the picker's Save button hit this every time; tapping the scrim never did, because the scrim is the dialog itself and arms no gesture. Promotion now needs 8px of travel — the conventional tap slop, well under what a deliberate pull covers in its first frames — in both the pointer and touch paths. The gesture's transition suppression is also scoped to a sheet that is open, so it cannot straddle an exit.
+
+ **The exit ran on the entrance's curve.** `--ease-standard` is `cubic-bezier(0.24, 1, 0.4, 1)`, a decelerate curve: it spends its speed immediately and coasts. Right for an entrance, wrong for an exit. Measured on device (iPhone, real Safari), a scrim tap put the sheet half off-screen in 59ms of the 410ms transition and 90% off in 163ms, with the dim gone before it — so the close was over before the eye could follow it. The closing state now carries an accelerating curve of its own, `cubic-bezier(0.3, 0, 0.6, 0.6)`: away from rest, gathering speed, quickest as it leaves the screen, and moving within ~50ms so it reads as one departure rather than a hesitation and a snap. Only the curve changes — the exit keeps `--duration-medium`, the entrance's band, which is what keeps it legible under a theme that scales the motion scale down (neutral's medium is 300ms against the base 410ms).
+
+ The scrim leaves with the sheet: while closing, the dim runs `linear` rather than the decelerate token. A fade covers no distance, so front-loading its progress just ends it early — the reasoning the touch date picker's surface swap already carries. `BottomSheetSwitcher` gets the same treatment when its flow closes; a handoff between two sheets is not a close and is unchanged.
+- `useListFocus` no longer swallows Escape when no `onEscape` was supplied. The hook called `preventDefault()` on every Escape — a habit inherited from the arrow keys, which share the handler and need it to suppress page scroll — so a list with nothing to dismiss still marked the key handled, and a surrounding layer that defers to `defaultPrevented` (a focus trap, a native popover) never got its turn. Escape is now consumed only when an `onEscape` is passed. Arrow, Home and End handling is unchanged (#5346).
+ Behaviour change: `AvatarGroup`, `ButtonGroup`, `Outline`, `Pagination`, `SegmentedControl`, `TabList` and `Toolbar` pass no `onEscape`, so an Escape pressed inside one of them now reaches the surrounding layer and can dismiss it — the point of the fix, but a host that counted on the key stopping there will notice. `NavHeadingMenu` does the same when it renders without a menu close handler. Menus and flyouts that do pass `onEscape` are unaffected. `patch`, not `[breaking]`: the swallowing was never a contract — the hook documented Escape only as "custom callback", and no component advertised consuming the key.
+- TabList: the selected tab now carries `aria-current="true"` — ARIA's generic "current item within a set" — instead of `aria-current="page"`. The strip is a `<nav>` and stays one, but it is used to switch views in place at least as often as it is used to navigate, and on those uses `page` asserted a page change that never happened. Assistive tech announced the selected tab as the _current page_ even when nothing had navigated; it now announces it as the _current item_, which is true either way. A tab given an `href` still renders an anchor and still reads as a link — its current marker is just less specific than it was. No role changes and no new props. (#5347)
+
+#### Contributors
+
+Thanks to everyone who contributed to this release:
+
+- @cixzhang
+- @imdreamrunner
+
+---
+
# 0.4.6
#### New Features
@@ -22,6 +48,7 @@
Nothing else is published, on purpose. There is no export that forces a surface: the touch picker is reachable by being on a touch device, which is the only place it is worth looking at. The media query the switch runs on is an internal constant, not an export — six other core components write `@media (pointer: coarse)` inline rather than sharing one, and nothing has asked to ask the same question. The picker's two sizes (the 44px day cell, the 28px wheel row) are compile-time constants rather than theme variables — the day size is an accessibility floor, and a variable a theme can quietly lower is not a floor. And the sheet's header button is addressed by a `data-` attribute rather than a theme target, because nothing has asked to restyle it. Each of those is additive later and awkward to withdraw once shipped.
The wheels also answer a mouse now. A wheel is a scroll container, so a finger pans it for free; a mouse got nothing, because browsers do not drag-scroll an overflow container — pressing and pulling on the one control shaped like a thing you spin did nothing at all. Dragging with a mouse works, and fixes a related bug on the way: BottomSheet begins its own drag from a `pointerdown` on its body and captures the pointer for it, so a click on a wheel row that wobbled more than a pixel or two used to select nothing.
+
- Export `useLocale` and `useCollator` for provider-backed formatting and comparison (#5194)
- RadioListItem: the `radio-list-item` row theme target now carries `size`, `selected`, and `disabled` state variants (matching `multi-selector-option`), so themes can style selected or disabled rows (#5143).
- RadioListItem: the `radio-list-item` theme target now rides the painting row element (converging with `list-item`), so a theme can style the row's hover background, padding, and border radius — previously it sat on a layout-only wrapper that painted nothing. The default (unthemed) row appearance is unchanged: it stays a bare surface with no row padding, radius, or hover/selected background (only the radio indicator tints on hover) (#5143).
@@ -42,6 +69,7 @@
On `Section` the matching `--container-padding-*` custom property moves with the prop, so bleed children (`Table`, `Divider`, a nested `Section`) keep compensating against the padding actually applied.
Existing code is unaffected: `padding`, `paddingInline` and `paddingBlock` behave exactly as before, and their generated class output is unchanged.
+
- Selector: add the `selector-option-row` theme target on the dropdown option row, carrying `size` plus `selected`/`disabled` state — so a theme can restyle row padding and density directly (mirroring `multi-selector-option`), instead of reaching the bare `role="option"` element with a structural selector (#5179).
- MediaTheme: add `mode="auto"` and `mode="off"` (#5299)
A theme is free to define `--color-background-inverted` as something that is not inverted — and a component that hardcodes `mode="dark"` then paints white text on pale grey at 1.25:1. The surface color is a runtime value and the mode was a compile-time guess, so no amount of care in the component could catch it.
@@ -51,6 +79,7 @@
When the backdrop is not knowable from CSS — during SSR, on the first client frame, and most often behind a `background-image`, whose pixels need sampling (see `useImageMode`) rather than a computed style — `auto` uses the new `fallback` prop instead of guessing.
Toast now uses `mode="auto"`, with its previous rule kept only as that fallback. Every stock Astryx surface renders exactly as before.
+
- Tooltip and HoverCard: tap to open where there is no hover (#5248)
Hover is the one trigger a touch screen cannot express, and both components were answering that badly. `Tooltip` suppressed itself on any device reporting `(hover: none)`, so its content — often the only label an icon button has — was simply unreachable on a phone. `HoverCard` did nothing at all: the `mouseenter` a tap synthesizes opened the card on every tap of its trigger, over the control the user was aiming at, with no gesture that closed it again.
@@ -71,11 +100,13 @@
The indicator also kept its negative overlap margin when it was the first child of a group, hanging 12px outside the group's own box. It now carries the same `:not(:first-child)` guard `Avatar` already had. And a negative `count` rendered the string `+-3` and announced "-3 more"; since the documented shape for the prop is `total - visibleCount`, which goes negative whenever the list is shorter than the slice, it now clamps at zero.
Docs: the guidance told readers to "set max to limit visible avatars", and there is no `max` prop. The API is compositional on purpose, so the consumer slices; the guidance now says that. The keyboard behaviour names the APG roving tabindex technique it implements, and `size` now says that the group's value wins over each child avatar's own `size`, including when the group leaves it at the default.
+
- Blockquote: the `cite` attribution renders as a bare `<cite>` instead of being wrapped in a `<footer>`, which was becoming a `contentinfo` document landmark. Also guards the slot with `isRenderable`, so `cite={condition && author}` no longer emits an empty `<cite>`, and wraps long unbroken words instead of overflowing (#5144).
- Bottom Sheet: float the grab handle so content sits closer to the top (#5222)
The drag area above the sheet's content was a 48px row in the sheet's flex column, pushing everything below it down by its full height and reading as an empty band above the first line of content.
The bar is now 24px and floats over the content: the scrolling area starts at the sheet's top edge and rides up under the pill, so a heading sits 24px closer to the top. The pill is 4px tall centered in the band, so it occupies only 10-14px from the edge — inside the top padding a content wrapper already provides — and a surface gradient behind it keeps it legible over whatever sits or scrolls beneath.
+
- BottomSheet: give the sheet one uniform edge against the scrim. Two things were wrong in dark mode. The sheet drew no edge of its own — surface and scrim sit a few RGB steps apart and the `--shadow-high` drop shadow is black on near-black, so the left and right edges were invisible (measured 1.16:1 boundary contrast in dark against 2.89:1 in light); it now carries a `--border-width` / `--color-border` hairline on its three scrim-facing edges, the same treatment MobileNav gives its scrim-facing edge. And under a theme that packs an inset ring into `--shadow-high` (every bundled theme adds one in dark mode) that ring was painted over by an opaque content wrapper such as `Section`, so it showed only in the gap below where the content ended and the side edges appeared to change width partway down; the scrolling body now paints the surface across the sheet's whole inner box, hiding the ring evenly (#5305).
- Breadcrumbs: button crumbs keep the link's vertical padding, the variant reaches the item theme targets, and interactive crumbs paint the shared focus ring (#5332)
- DateInput's touch calendar no longer rests between two months (#5319)
@@ -86,6 +117,7 @@
The rest position is now corrected rather than trusted: once the gesture is genuinely over — touch released, the scroller quiet, AND its offset confirmed unchanged across a frame — a scroller that is off a pane boundary is moved to the nearest one. A scroller the browser snapped for itself is left alone, so nothing extra happens on Chrome, and sub-pixel drift on a fractional viewport is ignored.
That last condition is what keeps the fix from becoming a worse bug than the one it fixes. A quiet period is not proof of rest: iOS runs its own snap animation for a few hundred milliseconds after the finger lifts and fires scroll events irregularly while it does, so a correction that trusts quiet alone can land mid-animation, round an offset still travelling toward next month back to the month it came from, and reverse the swipe.
+
- A disabled element answers the pointer with `default`, never an interactive cursor. Every `cursor` in core and lab carries `':is(:disabled,[aria-disabled="true"])': 'default'`, and the reset gives the same cursor to any disabled element that declares none — `[aria-disabled]` included, which previously got nothing. A lint rule and a Chromium sweep over every story keep it that way. Disabled elements sealed behind `pointer-events: none` are unchanged: the pointer never reaches them, so their cursor comes from an ancestor — which is why the guarantee is `default` rather than a distinct disabled cursor the library could only paint on some of them (#5323).
- Disabled elements no longer paint a hover state: every self-`:hover` in core and lab, and every `:hover` a theme authors, now carries the zero-specificity guard `:hover:where(:not(:disabled,[aria-disabled="true"]))`, so existing overrides weigh exactly what they weighed before. A lint rule and a Chromium sweep over every story keep it that way (#5247).
- InputClearButton: the clear (✕) affordance now meets the WCAG 2.5.8 AA 24×24 minimum on touch. The shared button rendered a 20px glyph with a 20px tap target, so every input that clears through it — Typeahead, Tokenizer, FileInput and the rest of the family — was under the floor on a phone. An `::after` overlay now expands the tappable region to 24×24, gated behind `@media (pointer: coarse)`: on a fine pointer the overlay is not generated at all, because a mouse is precise enough, an unconditional overlay could overlap neighboring controls in dense desktop layouts, and an overlay covering the button would take hover away from the `astryx-input-clear-icon` theme target. The visual glyph is unchanged at every breakpoint, and the overlay stops at 24px so it stays clear of the 8px adornment gap and the input's own caret area (#4956).
@@ -97,6 +129,7 @@
The reset now lives in one place (`overlayPaddingReset`, exported from `@astryxdesign/core/Layout`) instead of being hand-copied per overlay, and moved onto the `useLayer` root, which covers every layer surface at once. Values descendants subtract are zeroed; values they add are cleared to `initial` so readers fall through to their own default rather than losing their padding.
Section's padding propagation moved from the public `--astryx-section-padding` token to a private `--_section-padding-propagated`. The two carried different authority under one name — a theme's value versus one ancestor's — and an overlay could not drop the inherited one without blanking the theme's. Propagated values still win over the theme for nested sections, so behavior is unchanged. Themes are unaffected: `--astryx-section-padding` remains the public token and still reaches inside overlays.
+
- Theming: a physical `paddingTop`/`paddingBottom` now reaches the container padding expansion, so `card`, `dialog`, `section` and `number-input` track it the way they already track the logical spellings. A physical block longhand matched none of the padding property names the expansion recognizes, so it landed raw on the element while the component's internals kept reading the default — the NumberInput stepper column came up ~10px short of the field edges, and container bleed compensated by the wrong amount. Mixing spellings was worse than either alone: `padding: '10px'` plus `paddingTop: '14px'` published 10px in the tokens while the element painted 14px on top. `padding-top` and `padding-bottom` ARE the block edges in every horizontal writing mode, so this normalization assumes no direction. `paddingLeft`/`paddingRight` are deliberately unchanged: they are direction-relative — left is inline-start in LTR and inline-end in RTL — and the tokens are consumed by logical properties, so routing them would silently move the padding to the opposite edge under RTL. They keep their physical meaning, exactly as before (#5244).
- `DateInput`, `DateTimeInput`, `DateRangeInput`, and `Calendar` now format and parse dates using the ambient `InternationalizationProvider` locale instead of the host/browser locale. `plainDateFormat` (backing `formatSharedDate`) previously called `Intl.DateTimeFormat(undefined, ...)`, and `dateParser`'s day/month disambiguation heuristic for ambiguous numeric input (e.g. `3/4/2026`) called `Intl.DateTimeFormat()` with no locale at all, so a tree wrapped in a non-English `locale` still formatted and parsed dates using the host locale (#5120).
- Use the InternationalizationProvider locale for sorting, formatting, and speech defaults (#5195)
@@ -107,11 +140,13 @@
Locking background scroll hides the document's scrollbar. Where that scrollbar takes layout space — Windows/Linux desktop, and macOS set to always show scroll bars — hiding it widened the layout viewport by its width (~15px), so the whole page reflowed sideways behind the overlay and back again on close.
Both scroll locks now hold that gutter open with `scrollbar-gutter: stable` for the duration of the lock, which keeps `position: fixed` chrome (sticky headers, toast viewports) still as well as in-flow content. Pages with no space-taking scrollbar, and pages that already set `scrollbar-gutter` themselves, are left alone. Engines without `scrollbar-gutter` support fall back to padding the measured difference.
+
- SegmentedControl: keep item labels on a single line, truncating overflow with an ellipsis instead of wrapping to multiple lines (#5035)
- Selector: `SelectorOptionData` gains `description`, and the closed trigger now shows the selected option instead of just its label. The two-line option row `SelectorOption` draws was unreachable from the `options` prop — the data type carried only `value/label/disabled/icon` — so consumers kept a side map of descriptions keyed by value and re-rendered the row through `renderOption`. `description` now sits on the option data and `DefaultOption` forwards it. On the trigger, the selected option's own `icon` renders in the closed state (`startIcon` still wins when set, so a pinned field icon never doubles up), which retires the app-side `startIcon={value === 'x' ? … : …}` mirroring of state the component already knows. `renderValue` is the seam for drawing the selection yourself — the description included (#5202).
[feat] Item: new `layout` prop — `'stacked'` (default, unchanged) or `'inline'`, which keeps the description on the label's line with the description ellipsizing first. The inline row centers its two lines rather than sharing a baseline: two font sizes on one baseline make a line box taller than either line, which would push a fixed-height host off its size token. Every row built on `Item` gets the axis, `SelectorOption` included.
[fix] Selector: the trigger is sized by padding rather than a fixed height, so it is the `--size-element-*` token for a one-line value (28/32/36) and exactly one text line taller for a two-line one (48/52/56). The token and a text line are both multiples of 4, so every trigger lands on the 4px rhythm and lines up with the Buttons and inputs beside it — and no prop chooses the height, the content does. It previously swapped the fixed height for a minimum whenever `renderValue` was passed, keyed on the prop being present rather than on the content needing the room: a one-line value measured 39px and a two-line one 58px at _every_ size, so the `size` prop stopped affecting the trigger at all. Inside an `InputGroup`, where the group pins the row, the relaxed height did nothing and the content bled 4px through its own border. The group owns the row now and the trigger clamps its own value box to it, so nothing a caller draws can paint over the rows above and below: a `SelectorOption` folds onto one line and ellipsizes, and any other node is cut off at the row's edge. The trigger also stops asserting a height floor of its own there, so a control sized above its group — `<InputGroup size="md">` around a `size="lg"` control — sits in the group's row instead of growing it. The trigger's line box is pinned to that same token rather than a ratio, so the coarse-pointer font bump — and any theme that changes `--font-size-base` — grows the glyphs without moving the control off its size token.
+
- `Slider` with `orientation="vertical"` now gets the same 24px touch hit area the horizontal one got: its track was still only 20px wide on coarse pointers, under the WCAG 2.5.8 AA minimum. The whole track is the tap target for both orientations — the fix that floored the horizontal track's block size did nothing for vertical, whose short axis is the inline one — so the inline size is now floored to 24px on touch, with the same `@media (pointer: coarse)` gate. The rail, fill, marks and thumb all center on the inline 50%, so nothing visible moves and desktop is untouched (#5173).
- `@astryxdesign/core/theme/syntax` is importable from a server component again: the presets are data, not client references (#5076).
The subpath's barrel carried `'use client'`, and it is the only entry point for the syntax module. React therefore replaced _every_ export with a client reference for a server importer — including `dracula`, `oneLight`, `allSyntaxPresets`, `syntaxTokenDefaults` and `defineSyntaxTheme`, none of which need a boundary. Reading a preset in a Next.js server module (deriving a code-block ground, emitting theme CSS at build time) got a proxy instead of data, so `preset.tokens` was `undefined` and the failure surfaced far from its cause — the same import under plain Node worked perfectly.
diff --git a/packages/core/package.json b/packages/core/package.json
index 4ddbf0e835..b68be6f358 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/core",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Astryx Core",
"description": "The component library. Accessible, themeable React components with built-in spacing, dark mode, and StyleX styling.",
"author": "Meta Open Source",
diff --git a/packages/lab/package.json b/packages/lab/package.json
index 70d83b43c7..4c3148e82f 100644
--- a/packages/lab/package.json
+++ b/packages/lab/package.json
@@ -58,7 +58,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19.0.0",
"react-dom": ">=19.0.0"
},
diff --git a/packages/richtext/package.json b/packages/richtext/package.json
index 6591780f91..0f386420ce 100644
--- a/packages/richtext/package.json
+++ b/packages/richtext/package.json
@@ -60,7 +60,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19.0.0",
"react-dom": ">=19.0.0",
"lexical": "^0.46.0",
diff --git a/packages/themes/butter/CHANGELOG.md b/packages/themes/butter/CHANGELOG.md
index 234405201b..5ad624f119 100644
--- a/packages/themes/butter/CHANGELOG.md
+++ b/packages/themes/butter/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-butter
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/butter/package.json b/packages/themes/butter/package.json
index abfa7e065e..6de325aeca 100644
--- a/packages/themes/butter/package.json
+++ b/packages/themes/butter/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-butter",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Butter Theme",
"private": false,
"description": "Warm, creamy yellows with a friendly blue accent. Playful enough for consumer surfaces, soft enough to stay readable.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/chocolate/CHANGELOG.md b/packages/themes/chocolate/CHANGELOG.md
index 84c8f65309..d02cfc73c6 100644
--- a/packages/themes/chocolate/CHANGELOG.md
+++ b/packages/themes/chocolate/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-chocolate
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/chocolate/package.json b/packages/themes/chocolate/package.json
index ba461f6dc3..2856301e47 100644
--- a/packages/themes/chocolate/package.json
+++ b/packages/themes/chocolate/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-chocolate",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Chocolate Theme",
"private": false,
"description": "Warm chocolate theme for Astryx — rich brown palette with Fraunces headings, Albert Sans body, and Lucide icons",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/gothic/CHANGELOG.md b/packages/themes/gothic/CHANGELOG.md
index 119c176f05..06a166b2bb 100644
--- a/packages/themes/gothic/CHANGELOG.md
+++ b/packages/themes/gothic/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-gothic
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/gothic/package.json b/packages/themes/gothic/package.json
index 8126a4d38d..bf1b3f061b 100644
--- a/packages/themes/gothic/package.json
+++ b/packages/themes/gothic/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-gothic",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Gothic Theme",
"private": false,
"description": "Deep blue-grays and a signature display serif. Dramatic and editorial, for surfaces that want to be remembered.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/matcha/CHANGELOG.md b/packages/themes/matcha/CHANGELOG.md
index c74744d4d5..23fedab993 100644
--- a/packages/themes/matcha/CHANGELOG.md
+++ b/packages/themes/matcha/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-matcha
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/matcha/package.json b/packages/themes/matcha/package.json
index bc72f71e33..ced2b419ba 100644
--- a/packages/themes/matcha/package.json
+++ b/packages/themes/matcha/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-matcha",
- "version": "0.4.6",
+ "version": "0.4.7",
"private": false,
"description": "Earthy greens with a calm, organic feel. Naturalistic and grounded, great for wellness or content-first apps.",
"author": "Meta Open Source",
@@ -51,11 +51,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/neutral/CHANGELOG.md b/packages/themes/neutral/CHANGELOG.md
index dbe53e7b1f..79e4fac34d 100644
--- a/packages/themes/neutral/CHANGELOG.md
+++ b/packages/themes/neutral/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-neutral
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/neutral/package.json b/packages/themes/neutral/package.json
index 180622e295..f04dd45e70 100644
--- a/packages/themes/neutral/package.json
+++ b/packages/themes/neutral/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-neutral",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Neutral Theme",
"private": false,
"description": "Restrained warm grays. Minimal and quiet, so the content stays the focus.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/stone/CHANGELOG.md b/packages/themes/stone/CHANGELOG.md
index cd05dcd85e..6b0586cd70 100644
--- a/packages/themes/stone/CHANGELOG.md
+++ b/packages/themes/stone/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-stone
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/stone/package.json b/packages/themes/stone/package.json
index a152ef3716..7e9d7b8fad 100644
--- a/packages/themes/stone/package.json
+++ b/packages/themes/stone/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-stone",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Stone Theme",
"private": false,
"description": "Warm stone and slate, earthy and understated, with just enough character to feel handcrafted.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/packages/themes/y2k/CHANGELOG.md b/packages/themes/y2k/CHANGELOG.md
index 1ba57fe2f1..db1ed4eff1 100644
--- a/packages/themes/y2k/CHANGELOG.md
+++ b/packages/themes/y2k/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-y2k
+# 0.4.7
+
+---
+
# 0.4.6
---
diff --git a/packages/themes/y2k/package.json b/packages/themes/y2k/package.json
index 9a27c2e5d2..2816e0329a 100644
--- a/packages/themes/y2k/package.json
+++ b/packages/themes/y2k/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-y2k",
- "version": "0.4.6",
+ "version": "0.4.7",
"displayName": "Y2K Theme",
"private": false,
"description": "Hot pinks, lime greens, and Poppins. Bubbly, playful, and unmistakably retro.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.4.6",
+ "@astryxdesign/core": "0.4.7",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.4.6",
+ "@astryxdesign/cli": "0.4.7",
"rimraf": "^6.0.1"
},
"module": "./dist/source.mjs"
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index a4d25dac64..1f9e339f81 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -569,7 +569,7 @@ importers:
packages/charts:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -683,7 +683,7 @@ importers:
packages/lab:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -723,7 +723,7 @@ importers:
packages/richtext:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -778,7 +778,7 @@ importers:
packages/themes/butter:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -788,7 +788,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -797,7 +797,7 @@ importers:
packages/themes/chocolate:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -807,7 +807,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -816,7 +816,7 @@ importers:
packages/themes/gothic:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -826,7 +826,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -835,7 +835,7 @@ importers:
packages/themes/matcha:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -845,7 +845,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -854,7 +854,7 @@ importers:
packages/themes/neutral:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -864,7 +864,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -873,7 +873,7 @@ importers:
packages/themes/stone:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -883,7 +883,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1
@@ -892,7 +892,7 @@ importers:
packages/themes/y2k:
dependencies:
'@astryxdesign/core':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -902,7 +902,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.4.6
+ specifier: 0.4.7
version: link:../../cli
rimraf:
specifier: ^6.0.1