Should we release 0.68.3?

[fortmarek]

Released, please refer to #29

---

Should we release 0.68.3?

Current Release: 0.68.2

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

Local commits to backport to main

[opayen]

We would like to have facebook/react-native@114d31f cherry-picked to 0.68.
It is a fix to a regression that was introduced in 0.68 (see facebook/react-native#33977)

[kelset]

a couple more commits got "requested" via facebook/react-native#34326

[kelset]

one more thing we want for the next patch: once this is merged on main facebook/react-native#34339 (and so it's validated that the changes are viable) a separate PR will be done against 0.68-stable to introduce the same changes. We want to wait until that PR is up & merged before proceeding with 0.68.3

[kelset]

PR for 0.68: facebook/react-native#34345