Should we release 0.71.16?

[lunaleaps]

Current Release: 0.71.15

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

Pick requests from the previous discussion

[joe-sam]

Apply stack Symbolication patch part 1 & 2 to 0.71-stable (#41377) (#42079) (original #40914).

react/react-native#42222

[hurali97]

Merged ✅

[cipolleschi]

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

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

[hurali97]

Merged ✅

[hurali97]

Disable bitcode for hermes react/react-native#42283

[hurali97]

Merged ✅

[hurali97]

Pick request from 0.71.14 patch which was stalled in the previous patch as well due to Holidays.

#87 (comment)

[lunaleaps]

There are merge conflicts on this pick for Hermes. I'd recommend the original requester make a PR against Hermes rn/0.71-stable and work with the original author to land before we pick it into 0.71.

Commented with this approach here: #87 (reply in thread)

Let's release without this pick for now as it isn't a release regression

[matinzd]

Please pick react/react-native@96ed119

This fixes the issue regarding the permission contracts on Android 14. 
Currently it’s blocking matinzd/react-native-health-connect#60 and anything related to this matter.

[matinzd]

@hurali97

[hurali97]

Picked this by having a separate PR: react/react-native#42662 ✅