Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

xstate v5 support #58

Open
UberMouse opened this issue Jan 9, 2024 · 5 comments
Open

xstate v5 support #58

UberMouse opened this issue Jan 9, 2024 · 5 comments
Labels
released on @next released on @next-major

Comments

@UberMouse
Copy link
Collaborator

Support for xstate v5 will soon be released on the @next tag
UberMouse added a commit that referenced this issue Jan 9, 2024
@UberMouse
feat(core): xstate v5 support
314e71c 
Updates xstate-tree to be compatible with xstate v5

Closes #58

BREAKING CHANGES: v1 style builders (buildView etc) have been removed, along with a handful of testing utilities and a behavioural change with children and final states. They will no longer be automatically from views and instead must be manually stopped using `stopChild`
UberMouse added a commit that referenced this issue Jan 9, 2024
@UberMouse
feat(core): xstate v5 support
036f362 
Updates xstate-tree to be compatible with xstate v5

Closes #58

BREAKING CHANGES: v1 style builders (buildView etc) have been removed, along with a handful of testing utilities and a behavioural change with children and final states. They will no longer be automatically from views and instead must be manually stopped using `stopChild`
UberMouse added a commit that referenced this issue Jan 9, 2024
@UberMouse
feat(core): xstate v5 support
4c7a57a 
Updates xstate-tree to be compatible with xstate v5

Closes #58

BREAKING CHANGES: v1 style builders (buildView etc) have been removed, along with a handful of testing utilities and a behavioural change with children and final states. They will no longer be automatically from views and instead must be manually stopped using `stopChild`
github-actions bot pushed a commit that referenced this issue Jan 9, 2024
@semantic-release-bot
release(version): Release 4.4.0 [skip ci]
db55dae 
# [4.4.0](v4.3.0...v4.4.0) (2024-01-09)

### feat

* **builders:** buildRoutingMachine ([4a522e7](4a522e7)), closes [#50](#50)
* **builders:** viewToMachine ([f02be21](f02be21)), closes [#51](#51)
* **core:** xstate v5 support ([4c7a57a](4c7a57a)), closes [#58](#58)
UberMouse added a commit that referenced this issue Jan 9, 2024
@UberMouse
feat(core): xstate v5 support
c143495 
Updates xstate-tree to be compatible with xstate v5

Closes #58

BREAKING CHANGE: v1 style builders (buildView etc) have been removed, along with a handful of testing utilities and a behavioural change with children and final states. They will no longer be automatically from views and instead must be manually stopped using `stopChild`
github-actions bot pushed a commit that referenced this issue Jan 9, 2024
@semantic-release-bot
release(version): Release 5.0.0 [skip ci]
6ff66e4 
# [5.0.0](v4.3.0...v5.0.0) (2024-01-09)

### feat

* **builders:** buildRoutingMachine ([4a522e7](4a522e7)), closes [#50](#50)
* **builders:** viewToMachine ([f02be21](f02be21)), closes [#51](#51)
* **core:** xstate v5 support ([c143495](c143495)), closes [#58](#58)

### Breaking changes

* **core:** v1 style builders (buildView etc) have been removed, along with a handful of testing utilities and a behavioural change with children and final states. They will no longer be automatically from views and instead must be manually stopped using `stopChild`
github-actions bot pushed a commit that referenced this issue Jan 10, 2024
@semantic-release-bot
release(version): Release 5.1.0 [skip ci]
36af0de 
# [5.1.0](v5.0.0...v5.1.0) (2024-01-10)

### feat

* **core:** xstate v5 support ([4c7a57a](4c7a57a)), closes [#58](#58)
github-actions bot pushed a commit that referenced this issue Jan 10, 2024
@semantic-release-bot
release(version): Release 5.1.0-next.1 [skip ci]
0738dc3 
# [5.1.0-next.1](v5.0.0...v5.1.0-next.1) (2024-01-10)

### chore

* **release:** update it on next ([3eab46e](3eab46e))

### feat

* **core:** xstate v5 support ([4c7a57a](4c7a57a)), closes [#58](#58)
@github-actions GitHub Actions
Copy link

🎉 This issue has been resolved in version 5.1.0-next.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@koordinates koordinates deleted a comment from github-actions bot Jan 10, 2024
@koordinates koordinates deleted a comment from github-actions bot Jan 10, 2024
@koordinates koordinates deleted a comment from github-actions bot Jan 10, 2024
@koordinates koordinates deleted a comment from github-actions bot Jan 10, 2024
@davidkpiano
Copy link

Let me know if I can help!

@UberMouse
Copy link
Collaborator Author

Thanks @davidkpiano but I've got it all done now :) Just need to start using it in Koordinates for a bit to see if there's any other changes needed before an official v5 release. Just happy I worked out an incremental migration path for us, was not looking forward to migrating 100+ machines in one go 😅

@burakakca
Copy link

Is the shipment of v5 coming soon?

@UberMouse
Copy link
Collaborator Author

UberMouse commented May 8, 2024 •
edited
Loading

Hi the releases under the @next tag (5.1.0-next.11) are basically ready to release as v5, just need to update documentation and add support for the xstate v5 inspector. So if you are interested I would use the @next tagged releases for now, there shouldn't be anymore breaking changes and if I do have to do one for the inspector support it will be low impact. We have been running it in production at Koordinates for months so it's stable.

Don't have any ETA on actually finishing up that work though, I can't use the v5 inspector at work so I've been lacking motivation to finish this up and get it across the line 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released on @next released on @next-major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@UberMouse @davidkpiano @burakakca