Should we release 0.71.5?

[kelset]

Released. Please refer to #60

Current Release: 0.71.4

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. facebook/react-native@1d22e29 (already on branch)
2. facebook/react-native@8d8b44a
3. facebook/react-native@cbaf4c8#r103992924 <-- Fix as local commit and bump RNGP
4. facebook/react-native@36cc71a
5. facebook/react-native@c0abff1
6. Bump Metro/CLI

• fix: correctly list ios devices and simulators react-native-community/cli#1863
• [0.73.x] Hotfix release 0.73.9 - sync watcher backends with 0.76.0 facebook/metro#949
  -> version:
  • @react-native-community/[email protected]
  • @react-native-community/[email protected]
  • @react-native-community/[email protected]

7. facebook/react-native@9aac13d

Local commits to backport to main

[cipolleschi]

Remove Ruby requirements:

• facebook/react-native@e57b6d1

[kelset]

facebook/react-native#36421

[kelset]

probably fix needed for RNGP: facebook/react-native@cbaf4c8

(we can do as local commit and bump RNGP)

[cortinico]

This has already been picked on the 0.71-stable branch (I see it in the history picked as cbaf4c8da295cb9235a978d39a0ae8bca314c6b2)

[kelset]

I mean the comment in the commit ;) we need to fix that

[kelset]

samsung lists + textinput issue: this week a fix should land

The larger change to minimize the number of spans emitted by React Native is currently being validated and is targeting next week to hit the main branch.

We should wait for it before doing a new patch.

[lachenmayer]

Hey there, it would be amazing if the Prevent native blob resource from being de-allocated prematurely commit could be released at some point. We still have to patch RN just for this (see my comment on the PR). Thank you!

facebook/react-native@36cc71a

[fortmarek]

We will try cherry-picking this and the commit will be included in the next patch if there are no merge conflicts 👍

[thymikee]

FYI, we ported a fix for listing iOS simulators and devices through CLI: react-native-community/cli#1863
This could be pulled to the next 0.71.x

[kelset]

this would mean bump to these versions right?

 - @react-native-community/[email protected]
 - @react-native-community/[email protected]
 - @react-native-community/[email protected]

[thymikee]

yuup

[fortmarek]

Hey 👋

Please create a new issue in the react-native repository with a reproducible sample instead 🙏 This discussion is not meant for reporting bugs unless they are major release issues.

[lunaleaps]

In response to facebook/react-native#36229, want to pick facebook/react-native@c0abff1 to fix the breaking change

Here is the corresponding documentation PR: facebook/react-native-website#3624

[robhogan]

A fix is in the pipeline for the significant Windows/Linux Metro regression reported in facebook/react-native#36387. We'll be releasing Metro 0.73.9 as a hotfix and then will need a CLI hotfix bump too - IMO this will be an important one to get into 0.71.5.

[kelset]

thanks for the headsup! we'll make sure we put it in 👍

[robhogan]

Hotfix released in Metro 0.73.9. CLI PR: react-native-community/cli#1886

[robhogan]

Metro 0.73.9 included in CLI 10.2.2. Updating 0.71-stable: facebook/react-native#36678

[kelset]

sorry Rob looks like we worked on this at the same time: facebook/react-native@4c3bc24 I'll close off your PR

[Rag0n]

Hey, it would be nice to pick crash fix facebook/react-native@9aac13d

[kelset]

I didnt' want to enforce the bump of cocoapods in a patch release since it might disrupt some folks' codebases - isn't it something you can do downstream? 🤔

[Saadnajmi]

Yep, planning to do it downstream anyway.