Potential v0.66.1 Patch Release about releases HOT 22 CLOSED

Pick and release, no rn release is ever fast and .0 releases have low adoption based on feedback. A point release is immediate and more trusted. 2 cents 😁

from releases.

I guess I should say there is no such thing as a fast rn .0 release, quite evidently there are fast point releases! That was super quick. Thanks @lunaleaps

from releases.

Please revert facebook/react-native@cb0e1d6 or pick facebook/react-native#32398

from releases.

I believe these both need testing but in the continued effort to make the iOS build experience better, these two from @barbieri replace the current workarounds with what appear to be real solutions:

facebook/react-native@a1c445a
facebook/react-native@51bf557

My only hesitation on those (other than "needs testing") is that I'm not sure of the implications with regard to transitive dependencies. Specifically:

• I'm not sure if those also bring in the requirement for cocoapods >= 1.11 or not,
• "deprecate the __apply_Xcode_12_5_M1_post_install_workaround() as it's not needed anymore, at least with recent versions of the dependencies, no patching is required with RCT-Folly" --> do we already transitively depend on "recent version" (and what are those minimum versions?)

So I'm not sure if they fit (or can be made to fit) for a patch release or should wait for 0.67, but they have landed on main branch at least

from releases.

0.66.1 is out: https://www.npmjs.com/package/react-native

from releases.

please revert facebook/react-native@1b0fb9b
Related Discussion
facebook/react-native#31461
facebook/react-native#28236 (comment)

from releases.

Hey guys, sorry about the lack of responsiveness on this thread. I think my big question here has been, since we're planning on releasing 67 (cutting this week), and there are roughly a month of changes from 66 -> 67, should we just focus on getting 67 with these changes?

Are there any issues here that fundamentally break 0.66 usage? I think the strongest contenders are:

• facebook/react-native#32398 - Android border visual regression
• facebook/react-native@1b0fb9b - a UX regression for pull to refresh (which to my understanding doesn't break usability but isn't very polished? @gaodeng correct me if i'm wrong)

But these don't feel like major usage breakages for 0.66?
True, the delta of changes between 0.66 and 0.67 may elongate release testing, I'm tempted to focus on releasing 67. Maybe if we see within a week that 67 has major release blockers, then I can start a patch release -- what do you guys think?

from releases.

Okay sounds good, I can create a patch today. I've updated this issue with the picks I'm going to be taking which are all already on main

from releases.

request (fix ios release build via xcode)
facebook/react-native@cc59a7c

from releases.

Kotlin and Gradle bump maybe if possible, if not maybe in 0.67:
facebook/react-native@9ae3367

from releases.

That PR (32398) hasn't landed (since you made it...2 hours ago :-) ) but I just looked and it looks great IMHO

from releases.

Let's have any 0.66.2 in this discussion: reactwg/react-native-releases#3

from releases.

Kotlin and Gradle bump maybe if possible, if not maybe in 0.67: facebook/react-native@9ae3367

Just to note that I'm running those locally in 4 react-native 0.66 projects (two of which have big e2e harnesses, 2 of which are deployed on app stores) and they work fine as far as I can tell, no breaks seen when I moved on those

[edit to add that's just a success report, probably doesn't make sense for a patch release as it's not fixing a bug in react-native, per se]

from releases.

Android appearance module fix
facebook/react-native@25a2c60

from releases.

please revert facebook/react-native@1b0fb9b Related Discussion facebook/react-native#31461 facebook/react-native#28236 (comment)

Has this been reverted on main?

from releases.

@svbutko I don't that will be included in 0.66.x. You can also upgrade gradle yourself.

from releases.

@svbutko I don't that will be included in 0.66.x. You can also upgrade gradle yourself.

That's for the RN template, if it won't be in 0.66.x I mentioned that it would be fine to include it in 0.67

from releases.

Kotlin and Gradle bump maybe if possible, if not maybe in 0.67: facebook/react-native@9ae3367

Just to note that I'm running those locally in 4 react-native 0.66 projects (two of which have big e2e harnesses, 2 of which are deployed on app stores) and they work fine as far as I can tell, no breaks seen when I moved on those

[edit to add that's just a success report, probably doesn't make sense for a patch release as it's not fixing a bug in react-native, per se]

Same thing, I just wanted to note about since there's no 0.67 discussion yet

from releases.

@mikehardy it has been merged so i think we good to pick

from releases.

@aliraza-noon indeed! @lunaleaps merged it in facebook/react-native@d1a33cd and since they own this issue I'll assume they know the pick, but I'm committing here to close the loop in this thread. 🚀

from releases.

-- what do you guys think?

The Android appearance module fix facebook/react-native@25a2c60 is a block for my app.

from releases.

from 0.63.4 to 0.66.1，encounter this：
ios/Pods/Headers/Public/RCT-Folly/folly/math.h:26:10: 'cmath' file not found
ios/Pods/Headers/Public/React-Core/React/RCTConvert.h:17:9: Could not build module 'yoga'

from releases.