Skip to main content
React Native follows a regular release schedule to deliver new features, improvements, and bug fixes to the community. Understanding the release process helps you plan upgrades and contribute to releases.

Release Schedule

React Native follows a time-based release schedule:

Major Releases

Annually - Contains breaking changes and major features

Minor Releases

Quarterly - New features and improvements

Patch Releases

As needed - Bug fixes and critical updates

Version Numbering

React Native uses Semantic Versioning (semver):
MAJOR.MINOR.PATCH
  |     |     |
  |     |     └─ Bug fixes, no breaking changes
  |     └─────── New features, backward compatible
  └───────────── Breaking changes
0.84.0 (Latest as of March 2026)
  • Major version: 0
  • Minor version: 84
  • Patch version: 0
0.83.2
  • Second patch release of version 0.83
0.83.1
  • First patch release with bug fixes

Current Releases

Latest Stable: React Native 0.84.0Key Changes:
  • Hermes V1 is now the default engine
  • Minimum Node.js version bumped to v22.11
  • React 19.2.3 integration
  • New Architecture improvements
  • Legacy Architecture cleanup

Recent Versions

Released: 2026Breaking Changes:
  • Minimum Node.js version: v22.11
  • Hermes V1 is now default
  • Removed microtask API from JSTimerManager
  • TurboModule breaking changes
  • Legacy Architecture removed on iOS by default
Added:
  • Enhanced Animated support with AnimationBackend
  • Web Performance APIs enabled
  • Background image styles (iOS & Android)
  • CSS filters (iOS)
  • IntersectionObserver support
  • Improved TypeScript support
Platform-Specific:
  • iOS: Prebuild enabled by default
  • Android: Improved accessibility
  • Android: Keyboard event support (onKeyDown/onKeyUp)
View full changelog →
Released: 2026 (Patch)Fixed:
  • Color scheme in appearance state
  • Asset URL handling with unstable_path param
  • Fetch response URL after redirect
  • Text clipping on Android 15+
View changelog →
Released: 2026 (Patch)Fixed:
  • Network error for FormData uploads with binary data
View changelog →
Released: 2026 (Minor)Added:
  • AnimationBackend initialization
  • IntersectionObserver (gated)
  • Web Performance APIs
  • React Native DevTools network inspection
  • Background image support
Changed:
  • Hermes artifacts published independently
  • Metro bumped to ^0.83.3
  • React 19.2 integration
View changelog →

Release Process

How Releases Are Created

1

Release Candidate (RC)

A release candidate is created from the main branch:
  • RC1, RC2, RC3… are published for testing
  • Community tests RC versions
  • Critical bugs are fixed in subsequent RCs
  • Typical RC period: 2-4 weeks
2

Community Testing

Partners and community members test the RC:
  • Partners run CI against RC
  • Community reports issues
  • Regressions are identified
  • Feedback provided in release discussion
3

Stable Release

When RC is stable:
  • Final version is tagged
  • Release notes are published
  • npm packages are published
  • Announcement is made
4

Patch Releases

Critical fixes are backported:
  • Cherry-picked to release branch
  • Patch version is published
  • Updated changelog

Release Roles

Release Crew

Meta engineers responsible for coordinating releases and ensuring quality.

Community Releasers

Community volunteers who help test and validate releases.

Partners

Partner companies test releases and provide feedback.

Contributors

Everyone who tests RC versions and reports issues.

Testing Releases

Using Release Candidates

To test a release candidate:
# Install specific RC version
npm install [email protected]

# Or upgrade existing project
npx react-native upgrade 0.85.0-rc.1
Release candidates are for testing only. Do not use them in production apps.

Providing Feedback

1

Test Your App

Upgrade your app to the RC version and test thoroughly:
  • Build for iOS and Android
  • Test all features
  • Run automated tests
  • Check for regressions
2

Report Issues

If you find problems:
  • Search existing issues
  • Create new issue with “0.85” label
  • Provide reproduction
  • Include environment info
3

Share Feedback

Join the release discussion:

Becoming a Community Releaser

Community releasers help coordinate releases: Responsibilities:
  • Test release candidates
  • Provide technical support
  • Help triage issues
  • Communicate with community

Apply to Help

Interested in becoming a community releaser? Join the Releases Working Group.

Upgrade Guides

Upgrading React Native

Use the React Native CLI upgrade tool:
npx react-native upgrade
This will:
  • Show what will change
  • Allow you to review diffs
  • Merge changes automatically
  • Handle conflicts

Manual Upgrade

For more control:
# Install new version
npm install react-native@latest

# Update iOS dependencies
cd ios && pod install

# Clean build folders
cd .. && rm -rf node_modules
npm install
Check the upgrade helper to see exactly what changed between versions.

Breaking Changes

v0.84.0 Breaking Changes:
  • Node.js: Minimum version is now v22.11
  • Hermes: V1 is now the default engine
  • TurboModules: Various breaking changes
  • iOS: Legacy Architecture removed by default
  • Android: Legacy classes removed

Migration Strategies

For large apps:
  1. Update to latest patch of current minor version
  2. Fix all deprecation warnings
  3. Update to next minor version
  4. Test thoroughly
  5. Repeat
Create a test branch:
  1. Branch from main
  2. Upgrade React Native
  3. Fix breaking changes
  4. Run full test suite
  5. Merge when stable
For production stability:
  1. Lock to specific version
  2. Only update for security fixes
  3. Plan upgrades during slow periods
  4. Test extensively before deploying

Deprecation Policy

React Native follows a deprecation process:
1

Deprecation Warning

Feature is marked deprecated with console warnings
2

Documentation Update

Docs show deprecation and migration path
3

Grace Period

At least one minor version with warnings
4

Removal

Feature is removed in next major/minor version

Long-Term Support (LTS)

React Native does not currently have an official LTS program. The community is encouraged to stay on recent stable versions.
Recommended approach:
  • Use latest stable version
  • Apply security patches
  • Upgrade regularly (every 2-3 versions)
  • Test RC versions before stable release

Release Resources

Releases Page

View all releases and changelogs

Upgrade Helper

Compare versions and see changes

Releases Working Group

Join release discussions

Changelog

Full changelog history

Monitoring Releases

Stay informed about new releases:
Subscribe to the React Native Blog
Follow @reactnative on Twitter

Contributing to Releases

Help improve the release process:
  1. Test Release Candidates - Try RC versions in your apps
  2. Report Issues - File bugs with reproductions
  3. Fix Bugs - Submit PRs for release blockers
  4. Update Docs - Help document breaking changes
  5. Share Feedback - Participate in release discussions

Release Roles & Responsibilities

Learn more about release roles and how to get involved.
React Native releases are a community effort. Your testing and feedback help make releases better for everyone!

Build docs developers (and LLMs) love