Road to 0.66.0

[lunaleaps]

The branch cut has happened.

Notice

• Current release candidate: v0.66.0
• Have an issue with current release candidate? File an issue and we will triage.
• Have a pick request for this release? Does it call under our pick request qualifications? If so please comment on this issue with the hash and justification.

Highlighted Changes in this release

• See Changelog
• Nightlies & Commitlies

Release Process

Checklist

• Generate changelog and update this issue: Changelog PR here
• Start a Google doc of blog post for release and invite contributors of release highlights to expand

When ready to publish stable

• Ship changelog
• Ship blog post
• Cut and ship new documentation version - pull request

Retrospective Topics

• We should update manual testing script to automatically build hermes versions of RNTestProject. Added support for RNTester in facebook/react-native@732ac17
• We should audit the testing instructions, it mentions checking Chrome Debugger...which isn't a use-case anymore for RNTester and RNTestProject and we probably want Flipper instructions
• @lunaleaps had bad experience with not being able to exit debugging experience on Android
  • We picked facebook/react-native@49b3b31 to help
• @tido64 found issues on iOS with Image warning for unhandled promise?
• Maybe we should add Release configuration tests to manual test script
• We need a way to get sense of scale of people testing RC
• Questions about Hermes debugging and new app screen, instructions on the new app screen don't make sense for new apps using Hermes?
• Can we update react-native cli to allow option to create Hermes template app -- it'll make testing a little easier
• Apple Silicon (M1) machines were still not widely available to help speed up testing needs (not many have one, Circle CI didn't have one either)

Release Status

0.66.0 (shipped!)

---

0.66.0-rc.4

• Make a tweet about this when ready to get more signal
• Upgrade upgrade-helper

Blocking issues for releasing 0.66.0-rc.4

• --npm on new template project missing performance.now in runtime facebook/react-native#32224 (solved via CLI update, no pick necessary)

Picks for 0.66.0-rc.4

• Don’t hard-code CocoaPods’s sandbox path facebook/react-native#32243: facebook/react-native@ef5ff3e
• Podfile.lock updater for releases: facebook/react-native@d3c7e20 + facebook/react-native@ec9e971
• Verify that the fix is in place in 0.66 that will not require this facebook/react-native@5f7deb5 --> fix already in place: facebook/react-native@309ee06

---

0.66.0-rc.3

• Make a tweet about this when ready to get more signal
• Upgrade upgrade-helper

Blocking issues for releasing 0.66.0-rc.3

• Hermes Debugger not stopping on breakpoints  #250 Determined this is not a release-blocker
• Undefined symbols for architecture arm64 #251

Picks for 0.66.0-rc.3

• Undefined symbols for architecture arm64: facebook/react-native@b0c8a4e

---

0.66.0-rc.2

Blocking issues for releasing 0.66.0-rc.2

• Waiting on 0.9 release of Hermes
• A question of Podfile.lock due to conflict from cherry-pick of Bump hermes cocoapod to 0.9.0: facebook/react-native@8e66f0b -- @lunaleaps not sure if I need to run pod update to commit

Picks for 0.66.0-rc.2

• Hermes 0.9.0
  • libjsi change to be able to link with Hermes 0.9.0: facebook/react-native@1bc885b
  • Revert Android specific max heap size Hermes GCConfig: facebook/react-native@a8ac5ea
  • Bump hermes npm to 0.9.0: facebook/react-native@66bd1e9
  • Bump hermes cocoapod to 0.9.0: facebook/react-native@8e66f0b
• Break caching issue for manual testing script: facebook/react-native@cae0637

---

0.66.0-rc.1

Blocking issues for releasing 0.66.0-rc.1

• run-ios in release configuration #249

Picks for 0.66.0-rc.1

• Address error logbox when connecting to Chrome debugger: facebook/react-native@49b3b31
• OSS: Fix $ENTRY_FILE check for non-Debug Xcode builds: facebook/react-native@945c5f7
• OSS: add Xcode 12.5 + M1 machines CocoaPods post_install workaround: facebook/react-native@ac4ddec
• Switch order of search libraries to fix M1 build error: facebook/react-native@329b026
• Fix dependencies for bumping OSS version: facebook/react-native@963254e

---

0.66.0-rc.0

Picks that are in 0.66.0-rc.0

• Bump @react-native/polyfills version: facebook/react-native@2550948
• Fix RNTester for iOS 15: facebook/react-native@ad9030c
• Prefer the local react-native-codegen package: facebook/react-native@362511d
  • When this is cherry-picked, we should also move react-native-codegen from the template to root
• Add Android 12 BLUETOOTH_ADVERTISE to PermissionsAndroid: facebook/react-native@2bcc6fa
• Fix tooling dependencies after bumping version: facebook/react-native@5d6484e @lunaleaps I reverted this because it doesn't work
• Add hermes testing to RNTester for manual testing script: facebook/react-native@732ac17

[r0b0t3d]

Please pick facebook/react-native@7edf927

Fix keyboardDismissMode="on-drag" on Android

[lunaleaps]

0.66.0-rc2 is out: https://github.com/facebook/react-native/releases/tag/v0.66.0-rc.2

[fkgozali]

0.66.0-rc.3 has been published! We decided to publish the next RC 3 to help validate the arm64 fix. Please give it a try.

The Upgrade Helper has been updated as well via react-native-community/rn-diff-purge@f848591

[DmytroKovalskyi-voypost]

I have error with 0.66.0-rc.1 on ios build

sed: Pods/RCT-Folly/folly/portability/Time.h: No such file or directory

I think it caused that i run pod install not from ios folder,
i run it from project folder via

pod install --project-directory=ios

is it possible to check path in script something like ?

    if [[ -f ios/Pods/RCT-Folly/folly/portability/Time.h ]]; then
        sed -i -e  $'s/__IPHONE_10_0/__IPHONE_12_0/' ios/Pods/RCT-Folly/folly/portability/Time.h
    fi
    if [[ -f Pods/RCT-Folly/folly/portability/Time.h ]]; then
        sed -i -e  $'s/__IPHONE_10_0/__IPHONE_12_0/' Pods/RCT-Folly/folly/portability/Time.h
    fi

I had the similar issue during build after installing "0.66.0-rc.3" version : " 'boost/operators.hpp' file not found " . I believe boost pod wasn't completely installed due to large size, at least in my case. After that, i manually added used in previous versions pod 'boost-for-react-native' to Podfile . It's solved the build issue for now, but I think it could be a better solution for this .

[KingAmo]

I have error with 0.66.0-rc.1 on ios build

sed: Pods/RCT-Folly/folly/portability/Time.h: No such file or directory

I think it caused that i run pod install not from ios folder,
i run it from project folder via
pod install --project-directory=ios
is it possible to check path in script something like ?

    if [[ -f ios/Pods/RCT-Folly/folly/portability/Time.h ]]; then
        sed -i -e  $'s/__IPHONE_10_0/__IPHONE_12_0/' ios/Pods/RCT-Folly/folly/portability/Time.h
    fi
    if [[ -f Pods/RCT-Folly/folly/portability/Time.h ]]; then
        sed -i -e  $'s/__IPHONE_10_0/__IPHONE_12_0/' Pods/RCT-Folly/folly/portability/Time.h
    fi

I had the similar issue during build after installing "0.66.0-rc.3" version : " 'boost/operators.hpp' file not found " . I believe boost pod wasn't completely installed due to large size, at least in my case. After that, i manually added used in previous versions pod 'boost-for-react-native' to Podfile . It's solved the build issue for now, but I think it could be a better solution for this .

i believe it is due to react-native-reanimated, i file a issue there software-mansion/react-native-reanimated#2434

[fkgozali]

@dmtrKovalenko @KingAmo I think facebook/react-native#32243 would help with your build issue, it will be in RC4

[fkgozali]

v0.66.0-rc.4 has been published as a stable release candidate! It solved all known remaining issues in v0.66.0, so if this is stable, we plan to promote it to a stable release next week. Please try it out!

[joe-sam]

Didn't see this make the list of cherry-pick request in the change log, so I'm guessing it was missed!
fix: compare the LogBoxData ignorePatterns with the right code (#31977)

[mikehardy]

@joe-sam the commit is facebook/react-native@a950634 - I'm guessing with rc4 already out for a few days and the RC process already having been quite long, that rc4 will ship and this will need a new notice on the 0.66.1 issue whenever that is created. Just a guess on my part, I am not a part of that process, just noting it so you keep on eye on things and re-post to 0.66.1 if needed. Cheers!

[kelset]

as per conversation here: facebook/react-native#32284 (comment)
there won't be an RC5 with that extra commit - I'll hide my comment

[lunaleaps]

0.66.0 is out. Please see #254 for any issues