-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
chore(next-release): version package (next) #3151
Open
github-actions
wants to merge
1
commit into
next
Choose a base branch
from
changeset-release/next
base: next
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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 Git ↗︎
|
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 23, 2025 21:35
105ceac
to
1371b30
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 23, 2025 22:10
1371b30
to
da043a0
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
2 times, most recently
from
January 23, 2025 22:24
a838d80
to
3feae8c
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 23, 2025 22:33
3feae8c
to
1aea611
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 24, 2025 15:59
1aea611
to
cc9093f
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 24, 2025 18:39
cc9093f
to
7a89dbc
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
2 times, most recently
from
January 24, 2025 21:59
07197fe
to
c1a2061
Compare
github-actions
bot
force-pushed
the
changeset-release/next
branch
from
January 25, 2025 00:37
c1a2061
to
3c78330
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 next, this PR will be updated.
next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onnext
.Releases
@skeletonlabs/[email protected]
Patch Changes
@skeletonlabs/[email protected]
Patch Changes
style
prop for Avatar component. (#3117)@skeletonlabs/[email protected]
Patch Changes
bugfix: Call custom event handlers provided in ZagJs's internal handlers (#3157)
Implement
style
prop for Avatar component. (#3117)Bugfix:
bind:pageSize
now correctly updates in combination withonPageSizeChange
handler. (#3157)