Release 0.10.0 #129
Merged
Release 0.10.0 #129
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
|
What I wrote in #127 (comment) still applies. Let's please include the breaking changes in #122 and #123 in this release. Otherwise we will release 2.0 next week, and that would be silly in my opinion. |
|
Actually, after talking with @c089 we agreed to keep it on 0.* for now. It will now be an npm package, but a bit clumsy one (the way of using it is not what you'd normally do with npm packages). Therefore we thought it might be better to not call it 1.0.0 for now, if there is an opportunity (and there is one, as this package is still on 0.* right now). |
thiemowmde
approved these changes
Oct 6, 2017
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.
Looks like I messed up and cannot reopen #127, then submitting again.
This should not be merged before #128 was, otherwise release notes are a lie.