Repository navigation
Version Packages - #5815
Merged
Merged
Version Packages#5815
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 19, 2026 13:48
8719de1 to
5cbbcfb
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 main, this PR will be updated.
Releases
@xstate/svelte@5.0.1
Patch Changes
6a7fa79Thanks @ybai08! - Thesnapshotstore returned byuseActor(…)now reads the actor's current snapshot whenever it gains its first subscriber. Before, if the actor changed while nothing was subscribed to the store (for example, while the only component reading$snapshotwas unmounted), the store kept showing the old snapshot until the next change.useSelector(…)already worked this way.@xstate/vue@5.0.2
Patch Changes
016daa7Thanks @ybai08! -useSelector(…)now updates its selected value when an actor errors. This also updates thesnapshotreturned byuseActor(…)anduseMachine(…), so itsstatusanderrorreflect the failure.