Should we release 0.72.7?

[huntie]

Released, please refer to #93

Should we release 0.72.7?

Current Release: 0.72.6

Conversations on this thread are limited:

• major release issues.
• qualified cherry-pick requests of commits on main that did not make the previous patch version.

Please include a link to the specific commit on main to be cherry-picked, for example: 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.
If the issue is a major release issues, please reference the issue here.

---

List of qualified picks

1. facebook/react-native@ae0d714 - picked
2. facebook/react-native@265af22 - picked
3. facebook/react-native@18c9797 - Symbolicate unhandled promise rejections facebook/react-native#41377
4. facebook/react-native@10c5192 - picked
5. facebook/react-native@4eed12b - Fix RNTestProject testing on Android facebook/react-native#41378
6. facebook/react-native@daedbe6 - Make the interop-layer work with components with custom name facebook/react-native#41376

Local commits to backport to main

[stianjensen]

Regression with rotation in animated values in RN0.72:
facebook/react-native@ae0d714
(explained here: facebook/react-native#36608)

[fortmarek]

Picked ✅

[malikzype]

On RN 72.5 and 0.72.6 with Xcode 15, we are facing an issue:

Similar Issues which are open yet -
facebook/react-native#38283
facebook/react-native#38140
react-native-tvos/react-native-tvos#575

Note: The issue is not replicating on 0.72.4 with XCode 15
Can we release a patch to fix this?

[cipolleschi]

Can you create a repro with all the libraries required?
Vanilla react-native apps do not suffer from that problem, but to fix it for everyone, I'll need a reproducer I can work with.

[malikzype]

Sure

[cipolleschi]

I found that one of the libraries causing this is react-native-gesture-handler. We have a PR to fix that.

RNGestureHandler may not be the only one, though.

[malikzype]

Great. I can help with a reproducer in a couple of days and shall post here.

[malikzype]

Just to confirm that even updating RN Gesture Handler, the issue remains the same.

[cipolleschi]

Please pick:

• Fix unstable RCTAppDelegate podspec facebook/react-native#41009 this stabilizes the React-RCTAppDelegate.podspec

[fortmarek]

Picked ✅

[majkpal]

Please cherry-pick this fix:

• facebook/react-native@265af22

At Chime X Software Mansion we need this fix to be cherry-picked as currently there is no option to upgrade to the next version ( this fix has not been released anyway) and we are blocked with our next project there.

[fortmarek]

Picked ✅

[liamjones]

The Gemfile specifies/enforces a range: https://github.com/facebook/react-native/blob/v0.72.6/packages/react-native/template/Gemfile#L4

[cipolleschi]

Please pick:

• facebook/react-native@daedbe6
• facebook/react-native@4eed12b

[fortmarek]

Both cause merge conflicts, created separate PRs:

• Make the interop-layer work with components with custom name facebook/react-native#41376
• Fix RNTestProject testing on Android facebook/react-native#41378

[cipolleschi]

merge: facebook/react-native#41276 or you can't release as CI won't be green.

[fortmarek]

Merged ✅

[vksgautam1986]

can we have this facebook/react-native#40914

[stianjensen]

Link to merged commit on main for that:

facebook/react-native@18c9797

[fortmarek]

This PR causes merge conflict, created a PR: facebook/react-native#41377

[szymonrybczak]

CLI Bump: facebook/react-native#41316

[fortmarek]

Merged ✅

[wfern]

Can we pick this: facebook/react-native@ab81c16?

[fortmarek]

The InspectProxy.js file was part of the metro-inspect-proxy package in the Metro repo and it only got moved after 0.72 release: facebook/react-native#39045

I don't think there's an easy way to pick this, so you might need to wait for the 0.73 release cc @huntie

[wfern]

Thanks for the info.

Yes, I think wait for 0.73 it's the best option too, I tried the new chrome debugger in the RC and it's amazing!

If I apply a patch from the commit I requested to metro-inspect-proxy it fixes the issue because I wasn't even able to see the hermes target in newer versions of chrome/edge. Even so, I can't debug properly on version 0.72 due to other errors that appear in the console, for example:

WARN Not connected to page: 29 , failed trying to handle event: ...

​

[liamjones]

It was suggested that the webp vulnerability patched in Fresco should probably be backported to supported versions of RN - just adding a note here for reference: react-native-community/discussions-and-proposals#725 (comment)

[tido64]

I have a couple of fixes for pnpm repos that would be great to include. They've landed on main, but required some minor adjustments for 0.72-stable:

• Correctly declare runtime dependencies facebook/react-native#41445
• Fix build_codegen! not finding @react-native/codegen in pnpm setups facebook/react-native#41456