Should we release 0.70.11?

[kelset]

Released, please refer to #77

Current Release: 0.70.10

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. bump to do:
   • Metro 0.72.4
   • CLI 9.3.3 react-native-community/[email protected] (commits)
2. facebook/react-native@cd56347

Local commits to backport to main

[kelset]

this is the 0.70 release, hiding

[kelset]

from @robhogan:

Nominate this one for the RN-side fix to facebook/react-native#36794 (to accompany a bump to Metro 0.72.4).

• Use Content-Location header in bundle response as JS source URL facebook/react-native#37501 (facebook/react-native@671ea38)

[kelset]

bump to do:

• Metro 0.72.4
• CLI 9.3.3 https://github.com/react-native-community/cli/commits/9.x

[kelset]

we only do new patch releases for versions within the support window

[cipolleschi]

@nikit-psl thanks for the question, but, as @kelset said, we are not supporting version 0.67.5 anymore.
We strongly suggest you and your team to allocate some time to upgrade to a newer version. We are putting a lot of effort in trying to make every release less disruptive from the update perspective so that the teams can consistently keep their apps updated.

[kelset]

it's already in 0.70.10 #66 (comment)

[kelset]

@harshad-kathiriya it's already in 0.70.10 -> https://github.com/facebook/react-native/releases/tag/v0.70.10

[joe-sam]

Prevent LogBox from crashing on long messages #38005
facebook/react-native#38005

[kelset]

tried cherry-picking, but the merge conflicts are fairly extensive. Please try to setup a PR directly against 0.70 branch so that we can merge in the next patch.