Skip to content
This repository has been archived by the owner on Jun 17, 2022. It is now read-only.

0.61.0 Discussion #144

Closed
grabbou opened this issue Sep 24, 2019 · 7 comments
Closed

0.61.0 Discussion #144

grabbou opened this issue Sep 24, 2019 · 7 comments
Labels
backport request Cherry picking a change into an existing release stable Stable version

Comments

@grabbou
Copy link
Member

grabbou commented Sep 24, 2019

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.0 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.

@grabbou grabbou added stable Stable version backport request Cherry picking a change into an existing release labels Sep 24, 2019
@tomtargosz
Copy link

Can we get facebook/react-native@a4fbb8e included? Currently In iOS 13 apps will crash if more than one action is performed on a Sharesheet.

@thymikee
Copy link
Member

facebook/react-native@9f0dede - fix for Gesture Handler, affecting React Navigation

@satya164
Copy link
Member

We should also revert facebook/react-native@d57cdac and facebook/react-native@3e4c5c0

Context: https://twitter.com/joelafiosca/status/1176731298007851009?s=20

@grabbou
Copy link
Member Author

grabbou commented Sep 25, 2019

Cherry-picking facebook/react-native@9f0dede that must have been skipped by a mistake. The facebook/react-native@a4fbb8e also sounds like a quick and helpful fix, including it as well.

--

@satya164,

We should also revert facebook/react-native@d57cdac and facebook/react-native@3e4c5c0

It seems to be an issue with the Bitrise, not React Native itself (no issues running iOS with XCode). According to the StackOverflow issue mentioned in the linked tweet:

Committing this file to source control will prevent unnecessary rerunning of those checks for each user opening the workspace. (37293167)

It doesn't mean it is required. I would like to get additional context on this commit from the @karanjthakkar and @hramos and whether they were aware of this.

@satya164
Copy link
Member

@grabbou according to the linked tweet, CIs like bitrise expect this file to be present. people can add it manually when they need, but imo there's no harm in keeping it if it can make it few cases easier.

@grabbou grabbou changed the title 0.61.0 Discussion 0.61.x Discussion Sep 25, 2019
@grabbou
Copy link
Member Author

grabbou commented Sep 25, 2019

I am with you on that @satya164.

Is the best solution to remove it from the template's .gitignore so that it is by default present when people commit to Git repository?

I don't think it has to be present by_default if it's automatically generated anyway

@grabbou
Copy link
Member Author

grabbou commented Sep 25, 2019

I have reverted them both. Shipping 0.61.1 right now.

@grabbou grabbou changed the title 0.61.x Discussion 0.61.1 Discussion Sep 25, 2019
@grabbou grabbou closed this as completed Sep 25, 2019
@grabbou grabbou changed the title 0.61.1 Discussion 0.61.0 Discussion Sep 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport request Cherry picking a change into an existing release stable Stable version
Projects
None yet
Development

No branches or pull requests

5 participants
@satya164 @grabbou @thymikee @tomtargosz and others