- Notifications
You must be signed in to change notification settings - Fork11
Release 1.0.0#45
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.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
fonsp commentedJan 16, 2024
fonsp commentedFeb 6, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
heyyyy simon 🐙 |
SimonDanisch commentedFeb 7, 2024
Ahh... There are a few small breaking changes I wish to have in 1.0, but they're not high priority so I keep postponing it :( |
fonsp commentedFeb 7, 2024
Hey Simon! Maybe those changes could be 2.0.0 or 0.2.0? It doesn't need to be soon, it would just be nice if thenext release is not 0.0.6, but 0.1.0 or 1.0.0. Because right now every release is a breaking change. Recently the 0.0.5 contained only new features and patches, but all dependent packages had to change their compat to support it. |
SimonDanisch commentedFeb 7, 2024
Ok, lets do it on next release :) |
workingdoge commentedApr 1, 2025
I'd like to rely on this package |
Let's release 1.0.0 (or at least 0.1.0) so we can use semver. (Right now every release is a breaking release.)
I also don't feel like this package is in a
0.0.xstate.