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 fixes issues with machine snapshots retaining methods during initialization failures and improves declaration emits for machines with registered actors and inline callbacks.
Users relying on machine snapshots with initialization failures or using machines with registered actors and inline callbacks may be affected.
Update to this version if you encounter issues with machine snapshots or declaration emits in machines with registered actors.
This alpha release improves snapshot handling in Vue and Solid, with better error exposure and subscription management. React store selectors now properly respect custom comparisons.
Vue and Solid users who rely on subscriptions or error handling may be affected by changes in snapshot behavior.
Review snapshot handling and subscription behavior in Vue and Solid implementations.
This release introduces improvements to subscription handling and snapshot behavior across Vue, Solid, and React. Key changes include better value retention during subscriptions and enhanced snapshot handling for error states.
Users of @xstate/svelte, Vue, and Solid may need to update their code to handle changes in subscription behavior and snapshot handling.
Review the changes in subscription behavior and snapshot handling if using @xstate/svelte, Vue, or Solid.
This alpha release improves subscription behavior and error handling in @xstate/store-solid, particularly for Solid and Vue integrations. It also enhances React store selector comparisons.
Developers using @xstate/store-solid with Solid or Vue may need to adjust to changes in subscription behavior and error handling.
Review subscription behavior and error handling if using @xstate/store-solid with Solid or Vue.
This release focuses on fixing issues related to async atoms, persistence, and event handling. It ensures proper dependency tracking, correct persistence order, and improved error handling for async storage operations.
Developers using async atoms, persistence, or event handling in XState Store may be affected by these fixes.
Update to this version to benefit from improved async atom handling and persistence fixes.
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 type inference for machine outputs and fixes type-checking issues for `xstate/fsm` imports. Machine output types are now inferred as a union of final states' outputs without requiring explicit `schemas.output` declarations.
Developers using `xstate/fsm` or relying on machine output type inference are affected.
Update to this version to benefit from improved type inference and `xstate/fsm` type-checking fixes.
This release fixes TypeScript declaration emit issues for machines and setups created with `setup({ states })`, ensuring compatibility with `declaration: true` builds.
Developers using TypeScript with `declaration: true` and exporting machines or setups created with `setup({ states })` are affected.
Update to this version to resolve TypeScript declaration emit issues.
This release fixes generic type helpers that were incorrectly restricting invocation transition metadata, state input, and transition children.
Developers using generic type helpers in XState may be affected by the previous restrictions.
Update to this version to ensure proper type preservation in configurations.
This patch release fixes metadata types in generic history values, snapshot nodes, and directed graph results, ensuring consistent type handling with `AnyStateNode` and `AnyTransitionDefinition`.
Developers using generic history values, snapshot nodes, or directed graph results in XState may be affected by type inconsistencies.
Update to version 5.33.2 to benefit from the fixed metadata types.
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 patch release addresses TypeScript type widening issues for `AnyStateNode` and `AnyStateNodeDefinition`, ensuring compatibility with tools like `@typescript-eslint`.
Developers using TypeScript with `AnyStateMachine` and tools like `@typescript-eslint` may have encountered type safety warnings.
Update to this version to resolve TypeScript type warnings related to `AnyStateNode` and `AnyStateNodeDefinition`.
This release introduces separate schemas for state and transition metadata, improves type safety for persisted snapshots, and enhances event handling in state transitions.
Developers using XState for state management and event handling will benefit from improved type safety and metadata schema flexibility.
Update to this version to take advantage of the new features and improvements.
This release introduces the ability to define separate types for state and transition metadata, enhancing type safety and flexibility in XState machines.
Developers using XState with TypeScript who need distinct types for state and transition metadata are affected.
Update to version 5.33.0 to take advantage of the new metadata type separation feature.
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 focuses on fixing delayed transitions and built-in effects in minified bundles, ensuring hook-owned actors persist across React StrictMode effect reconnects, and improving compatibility with duplicate XState package copies.
Developers using @xstate/react with minified bundles, React StrictMode, or multiple XState package copies may be affected.
Update to this version to benefit from the fixes.
This alpha release adds inspection capabilities to component-local stores in @xstate/store-react. The `useStore` hook now supports an `inspect` option for wiring up inspectors that remain stable across re-renders.
Developers using @xstate/store-react with component-local stores who want to inspect them are affected.
Consider using the new `inspect` option if you need to debug component-local stores.
This release focuses on fixing delayed transitions and built-in effects in minified bundles, improving React StrictMode compatibility, and enhancing graph utility flexibility.
Developers using minified bundles, React StrictMode, or graph utilities with duplicate XState package copies are affected.
Update to this version to benefit from the fixes and improvements.
This release introduces improvements to state contracts and context schemas, enhancing type safety and structural metadata in state machines.
Developers using state machines with complex context schemas and state contracts will benefit from enhanced type safety and structural metadata.
Review and update state machine definitions to leverage the new context schema refinement capabilities.
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.