The 1.0 is a lie: The complexities of releasing React Native
summary
Argues that 1.0 is a lie because releasing React Native involves dozens of manual steps not solved by a version number: branching, CI, changelog/blog/diffs, lots of manual testing, and coordination with Facebook’s mono repo. Notes concrete fixes: adding a release candidate phase since v60, tooling like upgrade-helper and CLI work, and frequent automation efforts; cites around 1,400 commits/month and painful cherry‑picking conflicts as the real blockers to a single “stable” 1.0.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:08Tales from the releaser
- 2:38Why we release stuff
- 4:19How we release stuff
- 6:51The RN complexities
- 11:08Let's review those steps
- 12:32Solving & Workarounding
- 16:32Let's sum up the situation
- 17:39Let me explain
- 20:52At the end of the day
related talks
23mThe work that you don't see
25mReact Native in Practice
27m22 - A year in Review for React Native
22m5 Lessons Learned From A Major React Native Upgrade
31mThe Final Push: Deploying React Native
05mLightning talk from Eric Sauter
27mBuilding a Product with React Native
35mBridging the Gap: How to use React Native in existing large native code bases