Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #2154

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Version Packages #2154

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 2, 2025

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

  • 792939f Thanks
    @segunadebayo! - Add support for navigate context property to handle custom
    router navigations when trigger is rendered as a link.

    Here's a React example usage with the tabs machine.

    const [state, send] = useMachine(
      tabs.machine({
        id: useId(),
        value: "nils",
        // use router.push to navigate to the selected tab
        navigate(details) {
          router.push(`#${details.value}`)
        },
      }),
    )

Patch Changes

@zag-js/[email protected]

Minor Changes

  • 792939f Thanks
    @segunadebayo! - Add support for navigate context property to handle custom
    router navigations when trigger is rendered as a link.

    Here's a React example usage with the tabs machine.

    const [state, send] = useMachine(
      tabs.machine({
        id: useId(),
        value: "nils",
        // use router.push to navigate to the selected tab
        navigate(details) {
          router.push(`#${details.value}`)
        },
      }),
    )

Patch Changes

@zag-js/[email protected]

Minor Changes

Patch Changes

@zag-js/[email protected]

Minor Changes

Patch Changes

@zag-js/[email protected]

Minor Changes

  • 792939f Thanks
    @segunadebayo! - Add support for navigate context property to handle custom
    router navigations when trigger is rendered as a link.

    Here's a React example usage with the tabs machine.

    const [state, send] = useMachine(
      tabs.machine({
        id: useId(),
        value: "nils",
        // use router.push to navigate to the selected tab
        navigate(details) {
          router.push(`#${details.value}`)
        },
      }),
    )

Patch Changes

@zag-js/[email protected]

Minor Changes

  • 792939f Thanks
    @segunadebayo! - Add support for navigate context property to handle custom
    router navigations when trigger is rendered as a link.

    Here's a React example usage with the tabs machine.

    const [state, send] = useMachine(
      tabs.machine({
        id: useId(),
        value: "nils",
        // use router.push to navigate to the selected tab
        navigate(details) {
          router.push(`#${details.value}`)
        },
      }),
    )

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

  • 2e4ae72 Thanks
    @segunadebayo! - TreeCollection: Add support for new methods:

    • getPreviousSibling: Get the previous sibling node of the given node.
    • getNextSibling: Get the next sibling node of the given node.
    • remove: Remove the given node from the collection.
  • 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

@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]

@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]

@zag-js/[email protected]

Copy link

vercel bot commented Jan 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
zag-nextjs ✅ Ready (Inspect) Visit Preview Jan 7, 2025 6:04pm
zag-solid ✅ Ready (Inspect) Visit Preview Jan 7, 2025 6:04pm
zag-svelte ✅ Ready (Inspect) Visit Preview Jan 7, 2025 6:04pm
zag-vue ✅ Ready (Inspect) Visit Preview Jan 7, 2025 6:04pm
zag-website ✅ Ready (Inspect) Visit Preview Jan 7, 2025 6:04pm

Copy link

pkg-pr-new bot commented Jan 2, 2025

Open in Stackblitz

@zag-js/anatomy

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/anatomy@2154

@zag-js/anatomy-icons

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/anatomy-icons@2154

@zag-js/docs

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/docs@2154

@zag-js/core

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/core@2154

@zag-js/store

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/store@2154

@zag-js/types

npm i https://pkg.pr.new/chakra-ui/zag/@zag-js/types@2154

commit: aa12fca

@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 8482b7d to d4812a7 Compare January 2, 2025 20:30
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from d4812a7 to 8cf3981 Compare January 3, 2025 16:19
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 8cf3981 to 97c9b6b Compare January 4, 2025 17:44
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 97c9b6b to 7588327 Compare January 7, 2025 11:25
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 2613325 to 0b75963 Compare January 7, 2025 14:12
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from 0b75963 to a1904dc Compare January 7, 2025 15:51
@segunadebayo segunadebayo force-pushed the changeset-release/main branch from a1904dc to 6d89c0f Compare January 7, 2025 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants