Should we release 0.71.15?

[fortmarek]

0.71.15 has been released. See discussion for 0.71.16

---

Current Release: 0.71.14

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

• Should we release 0.71.14? #87 (comment)
• Should we release 0.71.14? #87 (comment)
• Should we release 0.71.14? #87 (comment)

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

[hurali97]

Picked ✅

[cipolleschi]

Merge facebook/react-native#41277 or you can't release as CI will stay red.

[hurali97]

Picked ✅

[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)

[hurali97]

This is not valid anymore, context here: react-native-community/discussions-and-proposals#725 (comment)

[linpengfei]

please cherry-pick this fix:
facebook/react-native@9497203

[hurali97]

Picked ✅

[hurali97]

Need to merge this PR for CLI bump: facebook/react-native#41478

[hurali97]

Picked ✅

[cipolleschi]

CircleCI got broken yesterday due to Ruby and bundler. This is the fix:
facebook/react-native@479b4bb

[hurali97]

This #87 (comment) will be picked in the next patch, since we are near holidays and releasing new hermes version isn't trivial at the moment.

[lunaleaps]

Merge facebook/react-native#42106 to pin monorepo deps as we're doing this with 72, 73, and main.

However, 71 doesn't fully have the monorepo deps fleshed out, also a lot of the packages have been re-named since so i'm not sure it's that necessary to merge this. The only lib that I pinned was react-native-codegen which has been renamed and we aren't updating anyway. However, currently a * dep on react-native-codegen will pull in 0.70.7 when I'm assuming we want 0.71.6 (which is what I pinned in the PR)

[hurali97]

Picked ✅

[joe-sam]

Corrects LogBox to display the actual stack trace libraries instead of internal code on the debug thread for all custom errors during unhandled promises.
facebook/react-native#42079

[lunaleaps]

@joe-sam Do you mind making that PR with all the picks required -- I think the issue is also file restructuring that's happened since 0.71. @hurali97 will be releasing this next week Monday

[joe-sam]

Have created a combined pick PR as suggested. #42613.

[hurali97]

Thanks for the effort and we will pick this in the next patch as we have to release a patch ASAP based on the issue: facebook/react-native#42110

[scaraux]

Anyone knows when 0.71 next release is? I have the boost dep issue and can't bump to 0.72 for node engine version reasons...

[kelset]

@scaraux it's out: https://github.com/facebook/react-native/releases/tag/v0.71.15