chore: version packages (beta)#2550
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
c4aabb9 to
42d1830
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
42d1830 to
e891a46
Compare
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
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 next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
@react-spring/core@11.0.0-beta.1
Major Changes
#2467
8a06ca7Thanks @joshuaellis! - Breaking:onRestno longer fires when an active animation is retargetedCalling
spring.start()with a newtovalue mid-flight no longerinvokes the previous animation's
onResthandler.onRestisdocumented as called when the animation comes to a stand-still, and a
retarget is not a stand-still — the spring keeps moving toward the new
goal. The
start()promise still resolves withfinished: falseonretarget, so callers that need the old goal-abandoned signal can read
it there.
onRestcontinues to fire as before onreset, oncancel,and on normal settle.
Migration: If you relied on
onRestrunning on every retarget(e.g. for cleanup or analytics), inspect the
start()promise'sfinished: falseresolution instead, or move the side effect intoonChange.Patch Changes
@react-spring/animated@11.0.0-beta.1
Patch Changes
@react-spring/parallax@11.0.0-beta.1
Patch Changes
@react-spring/shared@11.0.0-beta.1
Patch Changes
@react-spring/three@11.0.0-beta.1
Patch Changes
8a06ca7]:@react-spring/web@11.0.0-beta.1
Patch Changes
8a06ca7]:@react-spring/rafz@11.0.0-beta.1
@react-spring/types@11.0.0-beta.1
@react-spring/mock-raf@11.0.0-beta.1