Integrate latest upstream RN versions of each stable branch into our RNW stable branches #13184
Closed
4 tasks done
Labels
Area: Developer Experience
Deliverable
Major item tracked for top-level planning in ADO
enhancement
Parity: React Native
RNW does not look or behave like upstream RN platforms
Milestone
RN upstream has a different matrix of stable branches they support than us, and lately they've been releasing more patch versions than we've kept caught up with. This can be a problem as RN app developers create new RN apps with the latest RN patch version of a stable release, then they add RNW which was tested on an older patch version.
At bare minimum we should assume we're only supporting developers on the latest patch versions of each stable branch, and I'm concerned there's noise in the issues opened against us because our stable branches have locked on older RN versions. So I think it's time for a pass over the stable branches, from RN 0.71 and up, doing the integrate into our stable branch, and therefore bumping our (minimum) dependency version on the latest patch from RN.
My hope is that these will be "easy" integrates as the upstream patches focus on ios/android specifics, but it's possible there may be some JS changes that we need to accept, which would be a great catch of our forked files drifting in a way that can lead to developer noise.
Tasks
Strategy
The text was updated successfully, but these errors were encountered: