Skip to content

Version Packages#3077

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages#3077
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Apr 12, 2026 •
edited
Loading

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

@zag-js/[email protected]

Minor Changes

  • 43c5c9b Thanks
    @segunadebayo! - - Fix time-only formatters (no year segment) never firing
    onValueChange — era is now only required when year is present.
    • Fix setSegmentValue reading stale displayValues. updateSegmentValue returns the new IncompleteDate directly
      so the commit check uses the fresh value.
    • Fix dayPeriod (AM/PM) arrow up/down not updating the visible segment when hourCycle changes at runtime —
      displayValues now re-sync to the new hour cycle while preserving in-progress edits.
    • Fix typing "A" / "P" on the dayPeriod segment not updating the visible AM/PM. The typing path was writing 12 for
      PM while every other code path uses 1, so the display silently stayed on AM.
    • Add hideTimeZone prop. The timeZoneName segment now renders automatically when the value is a ZonedDateTime,
      and can be hidden via hideTimeZone: true.
    • Arrow navigation and auto-advance after typing now reach read-only focusable segments (e.g. timeZoneName). Typing
      the final editable segment (e.g. "P" on dayPeriod) advances focus to the trailing read-only segment instead of
      staying put.

Patch Changes

@zag-js/[email protected]

Minor Changes

  • 68d3d5b Thanks
    @segunadebayo! - - Add CSS unit support for defaultSize, minSize, and
    maxSize. The splitter now accepts px, em, rem, vh, and vw in addition to percentages, and resolves them to
    percentages after hydration.

    const service = useMachine(splitter.machine, {
  panels: [
    { id: "nav", minSize: "240px", maxSize: "480px" },
    { id: "main", minSize: 30 },
  ],
  defaultSize: ["240px", "60vw"],
})
    • Add resizeBehavior per panel. Set to "preserve-pixel-size" to keep a panel's pixel size constant when the parent
      splitter group resizes. Leave at least one panel as "preserve-relative-size" (the default) so the layout can
      absorb the change.
    panels: [
  { id: "nav", minSize: 20 },
  {
    id: "main",
    minSize: "240px",
    maxSize: "480px",
    resizeBehavior: "preserve-pixel-size",
  },
  { id: "aside", minSize: 20 },
]
    • Allow non-panel children inside the splitter root for fixed toolbars, rails, or status areas that should not be
      managed as panels. Use partial trigger ids ("left:", ":right") to bind handles around the fixed element.
    <div {...api.getRootProps()}>
  <div {...api.getPanelProps({ id: "left" })}>Left</div>
  <div {...api.getResizeTriggerProps({ id: "left:" })} />
  <div style={{ flex: "0 0 180px" }}>Fixed sized element</div>
  <div {...api.getResizeTriggerProps({ id: ":right" })} />
  <div {...api.getPanelProps({ id: "right" })}>Right</div>
</div>

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

  • 6dbc33a Thanks
    @segunadebayo! - Fix date input min/max handling to preserve entered segments while
    editing. Values are now clamped segment-by-segment on blur, so 06/15/1999 with min 2000-01-01 becomes 06/15/2000
    instead of snapping to 01/01/2000.

    Add constrainSegments to @zag-js/date-utils for segment-wise min/max clamping.

  • 8715c64 Thanks
    @segunadebayo! - Fix issue where the date input was not writable in locales whose
    date format separator contains more than one character (e.g. cs-CZ, sk-SK, hu-HU, ko-KR which use ". ")

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

  • 84b9e2b Thanks
    @segunadebayo! - - Add api.scrollTo(value, details?) for programmatically
    scrolling to a heading. The optional details.behavior controls the scroll behavior; when omitted, the platform
    default applies.

    api.scrollTo("installation", { behavior: "smooth" })
    • Rename getScrollEl context prop to scrollEl for consistency with other machines (e.g. initialFocusEl,
      finalFocusEl).

  • Updated dependencies []:

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

Patch Changes

  • 0973473 Thanks
    @segunadebayo! - Fix flip, shift, and hide middleware ignoring a late-mounted
    boundary. The boundary is now re-resolved on every computePosition tick, so a function-form
    boundary: () => element picks up the element once it mounts.

  • 020d79d Thanks
    @segunadebayo! - Forward boundary into the size middleware so available
    width/height match flip/shift, with per-tick resolution for function boundaries.

  • Updated dependencies [84b9e2b]:

@zag-js/[email protected]

Patch Changes

  • d729dc2 Thanks
    @segunadebayo! - Fix scroll lock leaking on <body> (data-scroll-lock,
    overflow: hidden) when nested dialogs or React Strict Mode trigger overlapping locks.
  • Updated dependencies [84b9e2b]:

@zag-js/[email protected]

Patch Changes

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

@zag-js/[email protected]

[email protected]

Patch Changes

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 12, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
zag-nextjs Ready Ready Preview May 17, 2026 7:18pm
zag-solid Ready Ready Preview May 17, 2026 7:18pm
zag-svelte Ready Ready Preview May 17, 2026 7:18pm
zag-vue Ready Ready Preview May 17, 2026 7:18pm
zag-website Ready Ready Preview May 17, 2026 7:18pm

Request Review

@segunadebayo segunadebayo force-pushed the changeset-release/main branch from a0967d2 to 103a84d Compare April 17, 2026 12:49
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 103a84d to 6c60149 Compare April 20, 2026 11:29
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 6c60149 to 84b0591 Compare April 20, 2026 12:00
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 84b0591 to 5e2c526 Compare April 20, 2026 12:27
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 09d7b38 to 0af56ec Compare April 26, 2026 14:45
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 0af56ec to c15d866 Compare April 29, 2026 09:12
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from c15d866 to acc62de Compare April 29, 2026 13:09
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from acc62de to 007ecf3 Compare May 1, 2026 14:28
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 007ecf3 to 6597f73 Compare May 1, 2026 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants