Should we release 0.66.3?

[lunaleaps]

Released, see discussion for 0.66.4

Current Release: 0.66.3

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

1. Fix npm latest tag when running patch update which needs:
   • Adding -v flag to bump-oss: facebook/react-native@b29b05f
   • Extract version parsing from release script: facebook/react-native@cc1e3ab
   • Clean up publish-npm.js and use parseVersion: facebook/react-native@029376c
   • Fix npm latest tag issue when releasing patches: facebook/react-native@68e6788
2. Revert jest preprocessor changes: facebook/react-native@74b91c5
3. Renames Keyboard.removeEventListener to Keyboard.removeListener: facebook/react-native@8880c09

Local commits to backport to main

[diegotsi]

Hey, I'm facing problems with Jest after upgrading from 0.65.1 to 0.66.2, it's the same problem related here, it's a serious issue because all unit tests are failing.

[lunaleaps]

@diegotsi @rubennorte is reverting the change and it's landing so we probably won't need facebook/react-native#32559

[diegotsi]

Ok, @lunaleaps! let me know when the new release was published and I can close the PR. thanks!

[makenova]

Also, does someone know why people are using the preprocessor in React Native directly in their Jest configurations? I thought that was specific for React Native tests, not to use externally in other projects (they should just use the Jest preset in the react-native package, which relies on metro-react-native-babel-preset and doesn't use the preprocessor).

This comment made me reevaluate my jest config.
I'm maintaining an old RN app and looks like I added the FB preprocessor 3 years ago when upgrading to 0.57.1.
Removing it does not seem to have any adverse effects and resolved an issue blocking my upgrade to 0.66.2

Removing the FB preprocessor does not seem to be a solution for everyone.

[diegotsi]

@makenova are you using styled-components?

[makenova]

@diegotsi no, I'm not.

[lunaleaps]

Will be releasing a patch tonight or tomorrow as soon as pending (see description) changes are in

[tapz]

0.66.3 seems to be out, but the version is added to the change log as "0.64.3".

[kelset]

thanks for mentioning - I took care of it https://github.com/facebook/react-native/releases/tag/v0.66.3

[kelset]

(and PR for changelog: facebook/react-native#32576)