0.61.5 Discussion

[grabbou]

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

[sibelius]

can we pick the new cli version?

react-native-community/cli#768

to improve support to monorepos on android?

[kelset]

@sibelius you don't need to wait for a new release for that, you can use yarn resolutions in your package.json as such:

  "resolutions": {
    "@react-native-community/cli-platform-android": "3.0.3",
    "@react-native-community/cli-platform-ios": "3.0.0",
    "@react-native-community/cli-tools": "3.0.0",
    "@react-native-community/cli-types": "3.0.0",
    "@react-native-community/cli": "3.0.4",
}

[grabbou]

You don't really need to do anything I guess. react-native depends on ^3.0.0, so it will get all the latest CLIs anyway, without any resolutions needed.

[narobertson42]

Please can you consider looking into PR below to resolve Android children pointerEvent issues

PR Request:
facebook/react-native#26374

Related Issues:
facebook/react-native#26099
facebook/react-native#27232
facebook/react-native#26147

[Aure77]

For accessibility purpose on touchable elements, can you cherry-pick this commit : facebook/react-native@68a10a5

PR: facebook/react-native#27293