Should we release 0.71.13?

[kelset]

Released, please refer to #87

---

Current Release: 0.71.12

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

Picked

1. facebook/react-native@3901688
2. facebook/react-native@f8c03d1
3. facebook/react-native@9157841
4. facebook/react-native@0c9c57a
5. facebook/react-native@177d97d

Local commits to backport to main

[Saadnajmi]

Pick request: facebook/react-native@f7219ec
Helps with JSC debugging

[fortmarek]

@Saadnajmi this cherry-pick causes merge conflicts. Do you think you can prepare a PR for this to 0.71-stable?

[Saadnajmi]

Draft here: facebook/react-native#38995

I also ran into some merge conflicts, so I want to do some testing before marking this as ready.

[Saadnajmi]

Should be ready now! I'm also going to port to 0.72 as I see I need to do that...

[fortmarek]

Picked 🤝

[dominikwagner]

Would it be possible to include the PR 38256 in this release? Because at the moment this is blocking Android 14 support.

[JMalone3]

Pick request: facebook/react-native@177d97d
Blocking Android 14 support. Please escalate. Our project has an OEM deliverable due early September with RN 0.71.

[fortmarek]

We plan to release 0.71 and 0.72 soon (ETA this or next week). Sorry for the wait!

[kelset]

just for reference to the release crew, this is the high-prior issue for MSFT that I mentioned at the last weekly sync that is getting looked into - once it's addressed we'd want to backport to 71 facebook/react-native#38024 (and 72 most likely)

[fortmarek]

Commit: facebook/react-native@3901688

However, there's a backport PR, we should cherry-pick instead.

[shivenmian]

+1 to this - now that the backport PR has been merged, would really appreciate this being picked in 0.71.13. cc @rasaha91

[fortmarek]

It's now picked and will be part of the next patch release

[kelset]

release crew specific improvement to merge asap (after patch is ok) -> facebook/react-native#38890

doesn't need a new patch, but merge for consistency across all versions in support window + main

[fortmarek]

Picked 🤝

[douglasjunior]

Pick request: facebook/react-native@0c9c57a

Fix onChangeText not firing when clearing the value of TextInput with multiline=true on iOS

[douglasjunior]

@kelset please, how do I know if this other commit was merged before?

facebook/react-native@a804c0f

Perhaps the two are complementary.

I've documented the multiline behavior between versions in this comment: facebook/react-native#36494 (comment)

[kelset]

when cherry-picking a commit you make an exact replica in the new branch, so the only way to figure it out is actually checking if the commit message appears in that git log of that branch. I usually do it via the GH interface for commit history, or via a git GUI client (fork in my case)

[fortmarek]

The other commit (facebook/react-native@a804c0f) seems to be already in 0.71, so we won't pick that.

We will pick the initial request.

[fortmarek]

Cherry-pick maven ping release improvement: facebook/react-native#38980

[fortmarek]

Picked 🤝

[AlexanderEggers]

Would it be possible to pick this commit? facebook/react-native@133ccdc

It would be great to get this small one into the next 0.71 patch release. It resolves an issue around the useEffect regression introduced in 0.69.

[edstbbz]

I would also like to see it in this release

[sunnylqm]

#69 (reply in thread)

[fortmarek]

We plan to release 0.71 soon, so this won't make it in 0.71.13. @cortinico any plans to backport this eventually to 0.71?

[cortinico]

Nope we're not planning on backporting this change to older versions. This is a really invasive fix and we feel that backporting it in a patch version of React Native 0.71 could create more harm than good.

[Saadnajmi]

Can we pick facebook/react-native#37914 and facebook/react-native#39037 ? The former allows direct debugging on JSC with iOS 16.4, while the latter makes the change backwards compatible to earlier versions of Xcode :)

[fortmarek]

We've already tested the current patch, so this will have to come in the subsequent one 😞

[Saadnajmi]

We've already tested the current patch, so this will have to come in the subsequent one 😞

No worries, thanks for the update!