Repository navigation
fix(scxml): preserve transition phases and script snapshots - #5819
Conversation
🦋 Changeset detectedLatest commit: 6f8d1f7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or 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 |
Why
Imported SCXML could run transition content after ancestor entry, repeat content across parallel regions, or execute scripts during
snapshot.can(...). Scripts that mutate declared arrays also failed on frozen development snapshots.What changed
In(...)state configuration.Scope
SCXML execution, a private core hook, documentation, and regression tests. Native transition semantics stay unchanged.
Blast Radius
The core hook runs only for imported SCXML machines. The Changeset covers both packages so their release stays compatible.
Verification
pnpm test --silent --maxWorkers=1passes all 272 files and 4,520 tests. Parallel runs hit the existing declaration setup's 30-second timeout; all 20 declaration tests also pass alone.