Should we release 0.71.11?

[kelset]

Released, please refer to #73

Current Release: 0.71.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. revert facebook/react-native@cd6a913
2. facebook/react-native@3681df2
3. facebook/react-native@f7e35d4
4. facebook/react-native@c05d822
5. facebook/react-native@671ea38
6. facebook/react-native@10d5588
7. bump: Metro 0.73.10 & CLI 10.2.4

Local commits to backport to main

[cipolleschi]

We will need this for Xcode15

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

[fluiddot]

It would be great if we could backport facebook/react-native@f7e35d4 (facebook/react-native#36121) to version 0.71.

[robhogan]

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

• 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.73.10
• CLI 10.2.4 https://github.com/react-native-community/cli/commits/10.x

[AlexanderEggers]

Would it be possible to backport facebook/react-native@3681df2? That fixes certain layout flatting issues. This issue is already fixed in 0.72 but it would be great to have that in 0.71 already.

[LcTwisk]

Just linking the layout flattening issue for anyone interested: facebook/react-native#37797

[kelset]

we tried to cherry pick it but it created significant merge conflicts so we are backing out to make sure we won't break things further. You can try submitting a PR yourself that does the cherry pick directly against the 0.71 branch so that we can review it and merge it for next patch (0.71.12).

[AlexanderEggers]

@kelset I created a cherry-pick here: facebook/react-native#37876

[onmotion]

Could we please backport facebook/react-native@c05d822 into release

[tido64]

Xcode defaults to 'Release' when running react-native run-ios under specific setups. This is fixed in @react-native-community/cli 10.2.4: react-native-community/cli#1957 (comment)

[AlexanderEggers]

Would it be possible to revert facebook/react-native@2558c3d which was introduced in the last RN patch version? This is causing quite a bit of side-effects with reanimated which needs to be patched manually. I would argue that such breaking impact should not be introduced in a patch release but should be reserved for larger package updates. Ref: software-mansion/react-native-reanimated#4548

[kelset]

this is fixed in reanimated 3.3.0? software-mansion/react-native-reanimated#4550

It doesn't sound like we did break anything, that commit is just a types fix for facebook/react-native#37543

[AlexanderEggers]

Yep that is correct but not every project can update to reanimated v3 yet.

[kelset]

note to self: we need to see if we can backport this facebook/react-native#37840 once it's merged, or manually revert facebook/react-native@cd6a913

[NickGerleman]

It would be great to backport facebook/react-native@3681df2 to fix facebook/react-native#37797.

[kelset]

was already asked here btw #70 (comment)

[kelset]

replying here too: we tried to cherry pick it but it created significant merge conflicts so we are backing out to make sure we won't break things further. You can try submitting a PR yourself that does the cherry pick directly against the 0.71 branch so that we can review it and merge it for next patch (0.71.12).