chore: version packages

[github-actions]

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.

Releases

@react-spring/animated@10.1.1

Patch Changes

• Updated dependencies [40baba5, 6110c76]:
  • @react-spring/shared@10.1.1
  • @react-spring/types@10.1.1

@react-spring/core@10.1.1

Patch Changes

• #2520 831a1bd Thanks @joshuaellis! - Floor the spring's adaptive precision at the smallest difference doubles can represent around the values being animated. Previously, when a caller's layout math introduced tiny floating-point drift on the target (e.g. Math.cos(Math.PI / 2) returning 6e-17 instead of 0, so a "logical 160" arrived as 159.99999999999997), the adaptive precision collapsed to a value smaller than any delta the spring could express, so the animation never settled and the awaited start() promise never resolved. Closes #2208.

• #2532 4eed726 Thanks @joshuaellis! - Auto-start useTransition when props is a function. The function/deps form creates an internal SpringRef, which was assigned to every controller and treated like an injected ref, so the documented useTransition(data, () => ({ ... })) form never started its enter animation. useTransition now matches useSpring/useSprings: only an injected ref (via config.ref) defers auto-start, so useChain and StrictMode remounts keep working. Note: if you previously worked around this by calling api.start() manually on the function form, the transition now also auto-starts. Closes #2287.

• Updated dependencies [40baba5, 6110c76]:

  • @react-spring/shared@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/parallax@10.1.1

Patch Changes

• #2527 822ceb0 Thanks @joshuaellis! - Pin the Parallax container to its top-left corner (top: 0; left: 0). The container is position: absolute but previously set no offsets, so it inherited its static position. Host layouts that shift that position — such as the place-items: center in Vite's default index.css — pushed the viewport-height container below the viewport, giving the document its own scrollbar on top of the container's, hence the "double scrollbar". Closes #2255.

• Updated dependencies [40baba5, 6110c76]:

  • @react-spring/shared@10.1.1
  • @react-spring/web@10.1.1

@react-spring/rafz@10.1.1

Patch Changes

• #2536 40baba5 Thanks @joshuaellis! - Fix looping/sequenced animations freezing under @react-three/fiber's frameloop="demand". The three target drives rafz from r3f's render loop, which only runs while frames are requested via invalidate(). When a loop/to-array/delay animation reached a segment boundary, the spring went idle for the microtask gap while the next segment was scheduled — r3f's loop stopped and nothing restarted it, so the animation froze (and event-driven invalidate() calls couldn't help, since they're cancelled by r3f's same-frame decrement). rafz now exposes an onDemand signal that fires while it has pending frame work; the three target turns it into an invalidate() deferred to after the current frame, cleanly restarting r3f's loop. Demand mode is preserved — once the animation settles, the canvas sleeps again. No more invalidate()-in-events or useFrame workarounds needed. Closes #2402.

@react-spring/shared@10.1.1

Patch Changes

• #2536 40baba5 Thanks @joshuaellis! - Fix looping/sequenced animations freezing under @react-three/fiber's frameloop="demand". The three target drives rafz from r3f's render loop, which only runs while frames are requested via invalidate(). When a loop/to-array/delay animation reached a segment boundary, the spring went idle for the microtask gap while the next segment was scheduled — r3f's loop stopped and nothing restarted it, so the animation froze (and event-driven invalidate() calls couldn't help, since they're cancelled by r3f's same-frame decrement). rafz now exposes an onDemand signal that fires while it has pending frame work; the three target turns it into an invalidate() deferred to after the current frame, cleanly restarting r3f's loop. Demand mode is preserved — once the animation settles, the canvas sleeps again. No more invalidate()-in-events or useFrame workarounds needed. Closes #2402.

• #2529 6110c76 Thanks @joshuaellis! - Stop the string interpolator throwing Cannot read properties of null (reading 'map') when an output value contains no numbers. Strings like boxShadow: 'none' or an unresolved CSS variable that falls through as its literal var(--x) text now extract to no numeric tokens and interpolate gracefully instead of hitting a null String.match. Closes #2327.

• Updated dependencies [40baba5]:

  • @react-spring/rafz@10.1.1
  • @react-spring/types@10.1.1

@react-spring/konva@10.1.1

Patch Changes

• Updated dependencies [40baba5, 831a1bd, 6110c76, 4eed726]:
  • @react-spring/shared@10.1.1
  • @react-spring/core@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/native@10.1.1

Patch Changes

• Updated dependencies [40baba5, 831a1bd, 6110c76, 4eed726]:
  • @react-spring/shared@10.1.1
  • @react-spring/core@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/three@10.1.1

Patch Changes

• #2536 40baba5 Thanks @joshuaellis! - Fix looping/sequenced animations freezing under @react-three/fiber's frameloop="demand". The three target drives rafz from r3f's render loop, which only runs while frames are requested via invalidate(). When a loop/to-array/delay animation reached a segment boundary, the spring went idle for the microtask gap while the next segment was scheduled — r3f's loop stopped and nothing restarted it, so the animation froze (and event-driven invalidate() calls couldn't help, since they're cancelled by r3f's same-frame decrement). rafz now exposes an onDemand signal that fires while it has pending frame work; the three target turns it into an invalidate() deferred to after the current frame, cleanly restarting r3f's loop. Demand mode is preserved — once the animation settles, the canvas sleeps again. No more invalidate()-in-events or useFrame workarounds needed. Closes #2402.

• Updated dependencies [40baba5, 831a1bd, 6110c76, 4eed726]:

  • @react-spring/shared@10.1.1
  • @react-spring/core@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/web@10.1.1

Patch Changes

• Updated dependencies [40baba5, 831a1bd, 6110c76, 4eed726]:
  • @react-spring/shared@10.1.1
  • @react-spring/core@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/zdog@10.1.1

Patch Changes

• Updated dependencies [40baba5, 831a1bd, 6110c76, 4eed726]:
  • @react-spring/shared@10.1.1
  • @react-spring/core@10.1.1
  • @react-spring/animated@10.1.1
  • @react-spring/types@10.1.1

@react-spring/types@10.1.1

@react-spring/mock-raf@10.1.1

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
react-spring	Error		Jun 9, 2026 6:47am