sonntam / node-red-contrib-xstate-machine

A xstate-based state machine implementation using state-machine-cat visualization for node red.
MIT License
22 stars 8 forks source link

Bump xstate from 4.30.0 to 4.34.0 #75

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps xstate from 4.30.0 to 4.34.0.

Release notes

Sourced from xstate's releases.

xstate@4.34.0

Minor Changes

  • #3588 a4c8ead99 Thanks @​davidkpiano! - The actions raise and sendTo can now be imported directly from xstate:

    import { raise, sendTo } from 'xstate';
    

    // ...

Patch Changes

  • #3599 333f803f9 Thanks @​Andarist! - Fixed a regression that has caused machine.getInitialState(value) to not follow always transitions correctly.

xstate@4.33.6

Patch Changes

xstate@4.33.5

Patch Changes

  • #3559 ddbc9bc5c Thanks @​Andarist! - Fixed minor compatibility issues with TypeScript 4.8 in the codebase. This fixes the typechecking with TypeScript 4.8 in projects that don't use skipLibCheck: true.

  • #3563 e3c7a9caf Thanks @​Andarist! - Fixed an issue with not executing actions in response to received batched events when using predictableActionArguments.

  • #3520 95a6a06d0 Thanks @​Andarist! - Fixed a runtime crash when sending multiple events as an array to a service. It is not recommended to use this feature though as it will be removed in the next major version.

xstate@4.33.4

Patch Changes

  • #3549 768c4e938 Thanks @​Andarist! - Fixed an issue with not being able to send events to initially started child actors when using predictableActionArguments.

xstate@4.33.3

Patch Changes

  • #3540 121fad172 Thanks @​Andarist! - Fixed an issue that caused invoked actors to be created before resolving assign actions from entry of the same state when using predictableActionArguments flag.

  • #3541 6c081ab87 Thanks @​Andarist! - Fixed an issue with not being able to read the updated snapshot of a child when receiving and processing events from it and when using predictableActionArguments flag.

xstate@4.33.2

Patch Changes

... (truncated)

Commits
  • 7ce3da5 Merge pull request #3589 from statelyai/changeset-release/main
  • 143e8af Version Packages
  • 19cb3a3 Merge pull request #3641 from ShaswatPrabhat/documentation/lazy_context_intit...
  • fc7abce Update docs/fr/guides/context.md
  • 0b7f9a0 Update docs/guides/context.md
  • a3298cf Merge pull request #3506 from maciekmaciej/patch-1
  • 2252ae8 Update docs/guides/final.md
  • fac15ed Update docs/guides/context.md
  • c492680 Update docs/fr/guides/context.md
  • cfae7e4 Add lazy initialization in the context guides
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #79.