-
Notifications
You must be signed in to change notification settings - Fork 24.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
[0.47] Commits to cherry-pick into stable release #14840
Comments
This one too then, if we're aiming for a fully working Podspec in 0.47: 6c2beaf |
Thanks! Now we can also cherry-pick
9afb71f
as
it finally landed.
…On Fri, 7 Jul 2017 at 21:45 James Ide ***@***.***> wrote:
I went ahead and cherry-picked those three commits (1ef21ec
<1ef21ec>,
26f01fa
<26f01fa>,
6c2beaf
<6c2beaf>)
and pushed 0.47.0-rc.1. Think it will be good if people can start testing
the Podspec (and therefore RN 0.47 in general as well) early.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14840 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWcxuIIFp7h_lHPBq7BQc8fy6bPUVNcks5sLorVgaJpZM4OOy9u>
.
|
Please pick e43c061 which fixes another Podspec issue |
Picked e43c061 and sent 0.47.0-rc.3 to CI. (9afb71f is part of 0.47.0-rc.2). |
Documentation fix: 6e68f2d |
Could we pull 7e29b1f in? Binary websocket comms are broken on Android (since 0.46) otherwise. (eg robhogan/react-native-paho-mqtt#5). |
Cherry-picked 7e29b1f (fixes binary WebSocket messages) and 113e046 (exposes option to turn off .babelrc lookup algorithm instead of having to find and remove node_modules/**/.babelrc). The podspec documentation fix was already cherry-picked. 0.47.0-rc.5 is now in CI. |
@brentvatne asked for b8fafb4 to be cherry-picked into 0.47 |
please pick 63c2ab3 so that android toolbar works properly. |
I am wrapping up changelog for this release and cherry-picking those commits. Stable should be on its way pretty soon. |
If possible, cherry pick 471c9da which will fix a CSS issue in the site. This one doesn't need to go out to npm, so it's fine to cherry pick it after the cut. |
I'd like to nominate
(sorry for the run-around on #15318!) |
No description provided.
The text was updated successfully, but these errors were encountered: