-
Notifications
You must be signed in to change notification settings - Fork 112
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
Version 2.6.0 introduces a breaking change #49
Comments
JamieDixon
changed the title
Upgrading to 2.6.0 introduces a breaking change
Version 2.6.0 introduces a breaking change
Apr 28, 2016
I agree! |
Apologies for that. I didn't review carefully when merging PR #48. How about change it to: "react": "^0.14.0 || ^15.0.0",
"react-dom": "^0.14.0 || ^15.0.0" |
Thanks Tom. Much appreciated. Be well. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the 2.6.0 release, React 15 is required.
This broke our codebase because 2.6.0 introduces a breaking change and our match for "^2.4.0" allowed for 2.6.0 to be installed without warning.
Since 2.6.0 introduces this breaking change I suggest the version be bumped to the next major version, 3.0 in line with semver.
What do you think? Thanks for react-toastr, we really appreciate all your work on this library!
The text was updated successfully, but these errors were encountered: