Should we release 0.72.10?

[huntie]

Should we release 0.72.10?

Current Release: 0.72.9

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

Local commits to backport to main

[joe-sam]

Corrects LogBox to display the actual stack trace libraries instead of internal code on the debug thread for all custom non-standard errors during unhandled promises. JavaScript allows to use throw with any argument, so technically our custom error classes don’t need to inherit from Error (e.g. third-party libraries).

facebook/react-native#42079

[huntie]

Picked ✅

[cipolleschi]

Fix for symbol not found _jump_fcontext with use_frameworks! (#39945):

• [RN][iOS] Fix symbol not found _jump_fcontext with use_frameworks! facebook/react-native#42228

[huntie]

Merged ✅

[cipolleschi]

Fix min ios version regression and updates podfile.lock:

• [RN][iOS] Fix min ios version regression and update podfile.lock facebook/react-native#42232

[huntie]

Applied locally (Podfile.lock conflicts) ✅

[cipolleschi]

Disable bitcode for hermes: facebook/react-native#42142

[huntie]

Merged ✅

[kirillzyusko]

Would be good to include facebook/react-native#42075 👀

It wasn't a problem to use install_modules_dependencies in RN 0.71 and in RN 0.73, but 0.72 can not use install_modules_dependencies (if library is using Swift code) and PR from above solves the problem (I hope it can be treated as qualified pick).