-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2025-01-17] Upgrade react-native
to 0.76
#48911
Comments
Sure! We’ll take care of that! |
I'll be helping with the upgrade |
I've asked people from Expo and SDK 51 is not compatible with RN 0.76 (it won't compile due to underlying changes). Given that, I believe it may be best to wait for the first beta release of SDK 52 (targeted at the first half of October) before we start the upgrade process. This way we don't have to hack around making SDK 51 compile on the current React Native version, which would have to be discarded anyway. What do you think? |
This makes sense to me. cc @roryabraham @mountiny @luacmartins |
Same |
Agreed |
agreed |
Self-assigning as I am happy to help push this ahead in EU timezone |
In progress |
This issue has not been updated in over 15 days. @AndrewGable, @j-piasecki, @mountiny, @staszekscp eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Still in progress |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
react-native
to 0.76react-native
to 0.76
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.82-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-01-17. 🎊 For reference, here are some details about the assignees on this issue:
|
Problem
The new
react-native
version 0.76 just was released 🎉https://github.com/facebook/react-native/releases/tag/v0.76.0-rc.0
It contains lots of bug fixes, improvements, and upgrades to the fundamental framework we are using.
Solution
Upgrade to
react-native
0.76cc @staszekscp @j-piasecki @WoLewicki - Per discussion in Slack, can you comment here so I can assign you to work on this? Thanks!
Issue Owner
Current Issue Owner: @j-piaseckiThe text was updated successfully, but these errors were encountered: