-
Notifications
You must be signed in to change notification settings - Fork 404
0.61.4 #151
Comments
Please cherry pick:
If 0.62 is not going to be re-cut, please pick this there as well. |
Please cherry pick
|
@thymikee, at this point, the conclusion is that we will not be re-cutting 0.62. I am going to release its preview now and will cherry-pick that one in the next iteration. |
I am going to work on 0.62 right now and will get back to this issue in few days (later this week) and we will release another update. |
CLI bump: facebook/react-native@e523302 |
Is this going to be backported? or is it scheduled for a later release? This is quite a big issue for us relying on cookies. |
Add this, please: Bump SoLoader to 0.8.0 This fixes RN support for Android Bundle. See here for one of the issues. To be short: SoLoader can't find libraries, when app is installed to device from a Bundle |
@niparx, unfortunately, this commit breaks 0.61.x branch so cannot be cherry-picked. But it's already there in RC 0.62. |
@radko93 0.62-stable branch does not actually have an RC tag or package release yet but if I understand correctly it is buildable / green on CI with the exception of a regression to the need for the android gradle library pickFirst workaround returning (until fixed) Not that that commit should be worked into 0.61.x or anything - just as information in case others are looking+waiting for that one |
Because 0.62 is going to wait for a few days, time to get back on this one and release fixes. Thank you @radko93 and @mikehardy for helping with the issues moderation! That is really appreciated! |
All commits cherry-picked. The release is on CircleCI and will be out soon. |
Closing as 0.61.5 is on CircleCI. Matter of ~30 minutes. |
Conversations on this thread are limited to 0.61 releases major issues and backport (cherry-pick) requests from commits that are already on master.
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.61.4 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.
The text was updated successfully, but these errors were encountered: