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):Version Examples
Version Examples
0.84.0 (Latest as of March 2026)
- Major version: 0
- Minor version: 84
- Patch version: 0
- Second patch release of version 0.83
- 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
v0.84.0 (Current)
v0.84.0 (Current)
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
- Enhanced Animated support with AnimationBackend
- Web Performance APIs enabled
- Background image styles (iOS & Android)
- CSS filters (iOS)
- IntersectionObserver support
- Improved TypeScript support
- iOS: Prebuild enabled by default
- Android: Improved accessibility
- Android: Keyboard event support (onKeyDown/onKeyUp)
v0.83.2
v0.83.2
Released: 2026 (Patch)Fixed:
- Color scheme in appearance state
- Asset URL handling with
unstable_pathparam - Fetch response URL after redirect
- Text clipping on Android 15+
v0.83.1
v0.83.1
v0.83.0
v0.83.0
Released: 2026 (Minor)Added:
- AnimationBackend initialization
- IntersectionObserver (gated)
- Web Performance APIs
- React Native DevTools network inspection
- Background image support
- Hermes artifacts published independently
- Metro bumped to ^0.83.3
- React 19.2 integration
Release Process
How Releases Are Created
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
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
Stable Release
When RC is stable:
- Final version is tagged
- Release notes are published
- npm packages are published
- Announcement is made
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:Providing Feedback
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
Report Issues
If you find problems:
- Search existing issues
- Create new issue with “0.85” label
- Provide reproduction
- Include environment info
Share Feedback
Join the release discussion:
- Releases Working Group
- Comment on release discussion
- Share success stories
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:- Show what will change
- Allow you to review diffs
- Merge changes automatically
- Handle conflicts
Manual Upgrade
For more control:Breaking Changes
Migration Strategies
Gradual Migration
Gradual Migration
For large apps:
- Update to latest patch of current minor version
- Fix all deprecation warnings
- Update to next minor version
- Test thoroughly
- Repeat
Test Branch
Test Branch
Create a test branch:
- Branch from main
- Upgrade React Native
- Fix breaking changes
- Run full test suite
- Merge when stable
Version Lock
Version Lock
For production stability:
- Lock to specific version
- Only update for security fixes
- Plan upgrades during slow periods
- Test extensively before deploying
Deprecation Policy
React Native follows a deprecation process:Long-Term Support (LTS)
React Native does not currently have an official LTS program. The community is encouraged to stay on recent stable versions.
- 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:Watch the React Native repository
Subscribe to the React Native Blog
Follow @reactnative on Twitter
Join Reactiflux Discord
Subscribe to React Native Newsletter
Contributing to Releases
Help improve the release process:- Test Release Candidates - Try RC versions in your apps
- Report Issues - File bugs with reproductions
- Fix Bugs - Submit PRs for release blockers
- Update Docs - Help document breaking changes
- 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!