Should we release 0.69.11?

[kelset]

Released, please refer to #72

Current Release: 0.69.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. Make CircleCI caches for hermesc be version dependent facebook/react-native#37452
2. facebook/react-native@10d5588

Local commits to backport to main

[kelset]

facebook/react-native#37452

[cipolleschi]

We will need this for Xcode15

• Add support for building with Xcode 15 facebook/react-native#37758

[robhogan]

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

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

[kelset]

we're in the process of releasing 0.69.11 - it will need to be done in 0.69.12 once the right bump of Metro/CLI will be out.

[robhogan]

Back in 0.69, Metro versions weren’t pinned - so for 0.69 only I think there’s value in picking this even before/without an explicit CLI bump - folks can get the benefit of the fix by reinstalling node_modules.

(No rush, of course - next time's fine)

[kelset]

we were already in the process of testing 0.69 branch when you posted this; so picking your commit and restarting would have slowed us down by quite a bit and we really wanted to push the 70 and 69 patches out today (we don't want to do releases on Fridays). But I'll add a note for next patch for sure.