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

0.61.5 Discussion #154

Closed
grabbou opened this issue Nov 23, 2019 · 7 comments
Closed

0.61.5 Discussion #154

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

Comments

@grabbou
Copy link
Member

grabbou commented Nov 23, 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.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.

@grabbou grabbou added stable Stable version backport request Cherry picking a change into an existing release labels Nov 23, 2019
@grabbou grabbou changed the title 0.61.5 0.61.5 Discussion Nov 23, 2019
@sibelius
Copy link
Member

can we pick the new cli version?

react-native-community/cli#768

to improve support to monorepos on android?

@kelset
Copy link
Member

kelset commented Nov 26, 2019

@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
Copy link
Member Author

grabbou commented Nov 27, 2019

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
Copy link

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
Copy link

Aure77 commented Feb 3, 2020

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

PR: facebook/react-native#27293

@nokite
Copy link

nokite commented Feb 19, 2020

hermesCommand in react.gradle uses wrong path. That's when you use a custom folder structure and do a release build with Hermes enabled. The issue comes from this line:

https://github.com/facebook/react-native/blob/0e4bcaa2960a2b1aa42dbe716fc6a35652aa7207/react.gradle#L33

I opened a new issue, but I think it's also relevant to mention here, as I read that this issue was fixed in the past, and might be returning.
facebook/react-native#28126

@kelset
Copy link
Member

kelset commented Mar 26, 2020

Hey folks, we've released 0.62.0 - refer to that as the latest stable release #179

@kelset kelset closed this as completed Mar 26, 2020
@react-native-community react-native-community locked as resolved and limited conversation to collaborators Mar 26, 2020
@kelset kelset unpinned this issue Mar 26, 2020
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

6 participants