For package consumers

Release notes

What shipped, why it matters, and anything you need to do when you upgrade Boreal UI.

Published packages

One version across the package family

  • @boreal-ui/core
  • @boreal-ui/next
  • @boreal-ui/types
  • @boreal-ui/docs
  • @boreal-ui/cli
  1. LatestBreaking changes

    v0.3.0

    Native forms, responsive controls, accessible tables, semantic themes, and more flexible Card and Modal composition across React Core and Next.js.

    What changed

    Native forms and shared validation

    Select supports real empty options, defaultValue, native resets, and repeated React 19 form submissions. TextInput, TextArea, and Select share feedback, stable ARIA associations, configurable errorLive announcements, and customization slots.

    Responsive controls and accessible tables

    Controls share height tokens and reliable fullWidth layouts. Button adds wrapLabel and retains independent sizing in grids. DataTable adds minWidth, tableLayout, caption-named keyboard-focusable scrolling regions, and nested-control row-click protection. Select improves RTL chevron spacing and SegmentedControl keeps focus outlines visible.

    Semantic themes and scoped overlays

    ColorScheme.semanticTokens supports explicit semantic roles, with derived defaults for palette-only themes and getThemeContrastIssues for opaque-color audits. Nested ThemeProviders create local scopes, and portals preserve their originating theme and live updates. Disabled controls gain readable colors and dashed boundaries.

    Card and Modal composition

    Card adds footer and padding="none". Modal accepts text and multiple children, supports padding="none", and derives accessible naming from visible string or number titles. Long dialogs keep scrolling bodies and reachable footer actions on narrow screens and at 200% zoom.

  2. PreviousNo breaking changes

    v0.2.11

    Component surface fixes for readable progress values, padded popovers, narrow segmented controls, stacked tabs, and tooltip outline variants.

    What changed

    Readable progress and popover content

    CircularProgress state values use contrasting text colors, and PopOver adds padding around its content in both Core and Next implementations.

    Narrow-container controls

    SegmentedControl options retain enough width for their labels, while Tabs apply consistent rounding to every tab when the group stacks vertically.

    Tooltip outline variants

    Tooltip now applies outline styling for variant="outline" and combines it with the glass surface for variant="glassOutline" in Core and Next.

  3. PreviousNo breaking changes

    v0.2.1

    Container-aware responsiveness and stronger component overflow checks, with refreshed compatibility and development documentation.

    What changed

    Container-aware layouts

    Components adapt to the space provided by their parent containers, with additional responsive coverage for Card, Pager, and other component families.

    Overflow and styling checks

    The library adds a component overflow audit and strengthens Core/Next style parity checks and documentation.

  4. PreviousNo breaking changes

    v0.2.0

    A broad reliability and accessibility release for keyboard navigation, overlays, SSR, data-heavy components, and package compatibility.

    What changed

    Keyboard and focus behavior

    Tabs, TreeView, menus, dropdowns, CommandPalette, MultiSelect, tooltips, and stacked modals now have stronger roving focus, dismissal, and focus-restoration behavior.

    Safer overlays and server rendering

    Floating panels and portal-based components gained SSR-safe geometry, shared outside-interaction handling, deterministic IDs, and a managed modal layer for nested dialogs.

    Data and input reliability

    DataTable received more dependable filtering, sorting, pagination, virtualization, and row identity, while FileUpload gained clearer validation and SSR coverage.

    Consistent styling and compatibility

    Core and Next styling were aligned across component families, transient surfaces now follow a shared elevation policy, and packed packages are verified across supported React, Next.js, and Node.js combinations.

  5. PreviousNo breaking changes

    v0.1.426

    A focused Accordion styling update that gives consumers a stable inner-content hook.

    What changed

    Accordion content styling

    Accordion now includes a contentInner class and a clearer content structure, making it easier to target expanded content without depending on internal markup.

  6. PreviousNo breaking changes

    v0.1.425

    A compatibility fix for MarkdownRenderer consumers using the current Marked API.

    What changed

    Markdown rendering fix

    MarkdownRenderer now calls Marked with its current API, preventing rendering failures caused by the previous call signature.

  7. PreviousNo breaking changes

    v0.1.424

    A security and resilience release covering rendered HTML, navigation, themes, file handling, and MessagePopup feedback.

    What changed

    Safer rendered HTML

    MarkdownRenderer sanitization was strengthened with sanitize-html, reducing risk when content includes HTML.

    Navigation and theme hardening

    Navigation targets, color-scheme values, theme initialization, and file-handling paths received additional validation.

    MessagePopup improvements

    MessagePopup behavior, styles, button states, and generated prop documentation were corrected for more consistent feedback UI.

    Package reliability

    Case-sensitive import paths, dependency versions, audit scripts, and the supported Node.js engine range were tightened for more predictable installs and CI builds.