Should we release 0.66.5?

[lunaleaps]

0.67.0 has been released

Please direct future discussion to here

Current Release: 0.66.4

Conversations on this thread are limited to 0.66 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 main but did not make the 0.66.4 cut, with a link to the specific commit hash on main with the commit to cherry-pick, like this example link: facebook/react-native@bd2b7d6

In other words, if you cannot point to a particular commit on main, then your request likely belongs as a new issue.

List of cherry picks

Local commits to backport to main

[billnbell]

Yes release 0.66.5 to fix the issue #6

[xiao99xiao]

@lunaleaps This may be a little off-topic but please don't use react/react-native@bd2b7d6 as the example, because it is a typical bad commit that ruined the onDismiss feature for several times because of being merged here and there, we took months across several releases and with this commit react/react-native@d85d5d2 to end the nightmare eventually.

[kelset]

good point, I've changed it to another example commit - thanks for noticing!

[billnbell]

OK can we release?

[lunaleaps]

Since we aim to release 67 in the next week or so, I'd rather focus our fixes and attention to that

[kelset]

In case we are going to consider a new patch for 0.66, this is one we might want to cherry pick react/react-native@6f12674 to solve this react/react-native#32463 (as pointed out by @cortinico in the last comment)

[cortinico]

Agree. With 0.67.x behind the corner, I don't think it's extremely crucial. But should we ship 0.66.6, having that included would be great 👍

[kelset]

yeah exactly, I'm just writing it for future memory

[tido64]

If we're doing 0.66.5, can we cherry-pick react/react-native@60cef85? iOS doesn't build if you run pod install --project-directory=ios.