Should we release 0.68.2?

[cortinico]

Current Release: 0.68.1

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@20b0eba

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 issue, please reference the issue here.

---

List of qualified picks

1. facebook/react-native@62ef6f5

Local commits to backport to main

[joe-sam]

The configuration option should in fact override the default but doesn't as described in issue 32239.
This appears to be an android only + hermes specific related bug for generating the intermediate packager sourcemap from configuration , which is apparently still present in react.gradle.

Unfortunately there is no related commit but the patch included does describes a simple one line fix.

[fortmarek]

Hey @joe-sam!

Can you create a new issue with reproducible steps with the latest version? We can continue the discussion there. Unfortunately, there's nothing we can cherry-pick until it gets fixed in main.

[joe-sam]

Sorry @fortmarek, thanks for your response. I understand that due process needs to be followed.
After examining and testing the patch I decided that it was not actually a one-line fix after all, therefore I have submitted a PR #33703 to resolve the issue, and to preserve the existing usual workflow behaviour also in order to avoid any breaking change, and we shall wait till it gets fixed in main before cherry-picking.

[pedrolopes10]

This one is merged in master:
facebook/react-native@c231d5e

[fortmarek]

Hey @pedrolopes10 👋

Thanks for the suggestion, however, this seems to be an optimization and not something that fixes a bug introduced in 0.68. I think we should wait with this for 0.69 unless this is somehow urgent (re: qualified picks)

[brunoducattii]

Hope that 0.68.2 will bring upgrades about enabling the New Architecture. This certainly will be a milestone for countries like Brazil where the average people has medium quality Androids. There are several new issues (even with iOS) about enabling it and app crashing: https://github.com/facebook/react-native/issues?page=2&q=is%3Aissue+is%3Aopen
Our company tried to handle with that for several weeks but because we are a lean startup we can't help putting more efforts to help the community. Thanks to everyone working on it!

Good luck.

[cortinico]

Thanks for your insigths @joaotmachado. We value user feedback as yours while we rollout the new architecture, and we're working hard to address them.

[kelset]

posting it here in order not to miss it - the PR that should properly fix the Windows + newArch issue (facebook/react-native#33528) is here: facebook/react-native#33707

[mateusz1913]

facebook/react-native@709a459 this fixes pod install errors for 3rd party "new architecture"-enabled with Swift code

[fortmarek]

Thanks for the suggestion, we have decided to cherry-pick this for 0.69.0 only instead (expect it in the next RC release)