-
Notifications
You must be signed in to change notification settings - Fork 404
0.57.7 Discussion #71
Comments
Could 53da585 be cherry-picked? |
Some other possible fixing cherry-picks
Maybe:
|
👍 on facebook/react-native@8d68a3e. That metro upgrade contains the Yarn PnP resolver that I really want to make use of. 😄 |
Another fixes:
Maybe:
|
hey everyone, thanks for the suggestions, I am thinking of releasing 0.57.8 by end of the week as last release for 0.57 for this year. I'll keep you updated. EDIT: I won't upgrade Metro because it relies on an alpha of Jest. You are free to enforce it in your local project, but for this branch we are trying to keep things as stable as possible. |
Oops never mind, got reverted. Will wait to find out what happened and get it back in. 🤦♂️ |
@levibuzolic that commit was reverted. So i don't think so. |
Hey everyone, just cherry-picked the commits, tested locally all everything went smoothly - now pushed to repo to test CI. You can see the list of commits here. Didn't cherry pick because created conflicts:
|
Release 0.57.8 is now on npm, I'll publish the changelog in a bit. Thanks to everyone who got involved, you can follow up the conversation for 0.57.8 in its dedicated issue. |
Conversation on this thread are limited to 0.57.7 release's major issues and backport (cherry-pick) requests from commits that are already on master - so that we can then produce a 0.57.8 release in the near future.
An example of a good such request is a bug fix for a serious issue that has been merged into master but did not make the 0.57.7 cut.
In other words, if you cannot point to a particular commit on master, then your request likely belongs as a new issue in http://github.com/facebook/react-native/issues.
If the commit you request to cherry pick is a complicated port, you will be asked to create the PR to the 0.57-stable branch yourself, in order to ensure that the process proceeds smoothly.
The text was updated successfully, but these errors were encountered: