-
-
Notifications
You must be signed in to change notification settings - Fork 232
Version Packages #2802
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
Merged
Merged
Version Packages #2802
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a1c4da6 to
fdd9423
Compare
fdd9423 to
7eb114e
Compare
07821ec to
36ecc74
Compare
36ecc74 to
fe71cb5
Compare
fe71cb5 to
1880524
Compare
1880524 to
aeb0567
Compare
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
@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
75f1899Thanks@segunadebayo! - Fix crash in range date picker when typing end date first by
adding
null/undefinedchecks when accessing date properties.@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
#2799
4b44542Thanks@nelsonlaidev! - Fix not working resize API
#2800
0f6e804Thanks@nelsonlaidev! - Export missing types
#2805
a766d97Thanks@nelsonlaidev! - Make the image cropper responsive
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]
Patch Changes
@zag-js/[email protected]
Patch Changes
5cae24cThanks@segunadebayo! - Revert to using
offsetLeft/offsetTopto fix indicatorpositioning in scrollable containers.
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
5cae24cThanks@segunadebayo! - Revert to using
offsetLeft/offsetTopto fix indicatorpositioning in scrollable containers.
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
71f8a73Thanks@segunadebayo! - - Fix issue where effects were not cleanup correct.
@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]
@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]
Patch Changes