-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Versioning? #1173
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Our latest is out on npm! |
I'm curious why this was treated as a breaking change. Instead, a new method and/or type could have been introduced. This approach prevents me from migrating my code incrementally. |
The old API is still in We opted to not add in new methods or types to decrease the size of the library. We were able to drop 55% of the library while adding more features than before. If we kept everything around the library would have been much larger. |
The changelog shows
4.0.0-rc.1
as the latest version, dated 2017-06-02.However, I also see a tag for
4.0.0-rc.2
.The current head version of
package.json
shows a version of5.0.0-rc.0
. There is no tag I can see corresponding to this.I'm having a hard time understanding what the latest version really is. If there is a
5.0.0-rc.0
, this would seem to imply to me that4.0.0
should have been officially released as4.0.0
with no-rc1
suffix.What is the current status of latest releases?
The text was updated successfully, but these errors were encountered: