Release 1.0.0 #45
Open
Release 1.0.0 #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
heyyyy simon 🐙 |
|
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 :( |
|
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 the next 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. |
|
Ok, lets do it on next release :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.