-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
[CHANGELOG] Prepare v4.11.2 #23813
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
[CHANGELOG] Prepare v4.11.2 #23813
Conversation
Details of bundle changes.Comparing: 328cdd4...076ca8a Details of page changes
|
|
For posterity: Still think this is a bad idea. Quite disappointed we're letting users blindly fall into this trap. |
|
@eps1lon I respect that, I can understand why. I'm happy you feel safe enough to voice this concern :). At least, I have updated the wording to stick to what we said initially, so no changes in policy :). I believe that keeping third-party dependencies up-to-date helps with the migration. I wish we could have React 17 as a selling argument to switch from v4 to v5 but considering how little breaking changes there are (mostly stubble changes around the event), I think that most teams will try to upgrade anyway. Our examples and codesandbox demo on v4 opens with React 17. |
Co-authored-by: Matt <github@nospam.33m.co>
No description provided.