what stackpulse tracks
XState releases from GitHub
StackPulse watches XState release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Actor-based state management and orchestration StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches XState release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This alpha release introduces several improvements and fixes, including better handling of child actors, enhanced TypeScript support, and the migration from `types` to `schemas` in machine configurations. It also includes various bug fixes and performance improvements.
Developers using the v5 `types` key in machine configurations will need to migrate to `schemas`.
Migrate from `types` to `schemas` in machine configurations to avoid compile errors.
This release improves error handling for async actions by routing rejected promises to actor error handlers, adds type helpers for error events, and introduces passive observers for lifecycle tracking.
Users relying on unhandled promise rejections in custom actions will need to add `onError` handlers to avoid actor errors.
Review and add `onError` handlers for custom actions that may reject promises.
This release introduces a breaking change to named guards, which are now plain predicate functions without the transition args object. It also fixes framework adapter snapshot inference for projects with `exactOptionalPropertyTypes` enabled.
Developers using named guards in XState are affected by the breaking change in guard function signatures.
Update named guards to explicitly pass values from `context` or the event.
This release introduces a new mechanism for handling invalid external events by rejecting them at the delivery boundary instead of causing errors or throwing exceptions. Rejections are reported through a new `onRejectedEvent` hook, inspection events, and development-mode console warnings.
Developers using external events with runtime validator schemas or handling internal event types sent from outside their owning actor are affected.
Update event handling logic to utilize the new `onRejectedEvent` hook and handle `@xstate.deadLetter` effects appropriately.