The latest stable release, the official support status of each version, the Expo SDK mapping, and how to check which version your app actually has installed.
Last verified September 13, 2026 against the npm registry, reactnative.dev/docs/releases, and docs.expo.dev. Next prerelease on npm: 0.88.0-rc.0.
The React Native team maintains the latest 3 minor series. Right now that means 0.87 and 0.86 (Active) and 0.85 (End of Cycle). Everything older is Unsupported.
| Version | Release date | Latest patch | Support status |
|---|---|---|---|
| 0.87 | August 10, 2026 | 0.87.1 | Active |
| 0.86 | June 9, 2026 | 0.86.3 | Active |
| 0.85 | April 6, 2026 | 0.85.3 | End of Cycle |
| 0.84 | February 9, 2026 | 0.84.1 | Unsupported |
| 0.83 | December 10, 2025 | 0.83.10 | Unsupported |
| 0.82 | October 6, 2025 | 0.82.1 | Unsupported |
| 0.81 | August 12, 2025 | 0.81.6 | Unsupported |
| 0.80 | June 12, 2025 | 0.80.3 | Unsupported |
| 0.79 | April 8, 2025 | 0.79.7 | Unsupported |
| 0.78 | February 19, 2025 | 0.78.3 | Unsupported |
| 0.77 | January 21, 2025 | 0.77.3 | Unsupported |
Scheduled next: 0.88 on October 12, 2026, 0.89 on December 7, 2026. Schedules can move.
Status and dates: reactnative.dev/docs/releases. Latest patches: npm registry. Verified September 13, 2026.
The official policy, from reactnative.dev/docs/releases, is a commitment "to maintain the latest 3 minor series." There is no separate long-term support line. The support policy defines three statuses:
Recent minors have shipped about every two months, so a version typically moves from latest to Unsupported within about six months. The table above shows the exact dates.
React Native 0.87.1 declares a peer dependency on React ^19.2.3 and requires Node.js ^22.13.0 || ^24.3.0 || >= 26.0.0, according to its package metadata on npm.
Bands based on the official support status. The work involved depends on your dependencies and native code as much as on the version number.
Officially active: these minors get regular patch releases. Keep taking patches and plan the next minor when it ships.
Fewer patches from here. The release crew ships one last patch before the next minor moves it to unsupported. Plan the upgrade now.
No new releases are expected. These versions already run only on the New Architecture, so the upgrade is mostly version and dependency work.
No new releases are expected. These versions could still run the Legacy Architecture, which was frozen in 0.80 and cannot be used from 0.82, so upgrading usually includes a New Architecture migration.
Status definitions: React Native releases support policy. Verified September 13, 2026.
Each Expo SDK targets one React Native version, so upgrading the SDK upgrades React Native. The newest SDK does not always target the newest React Native: SDK 57 targets React Native 0.86.
| Expo SDK | React Native | React | Minimum Node.js |
|---|---|---|---|
| 57 | 0.86 | 19.2.3 | 22.13.x |
| 56 | 0.85 | 19.2.3 | 20.19.x |
| 55 | 0.83 | 19.2.0 | 20.19.x |
| 54 | 0.81 | 19.1.0 | 20.19.x |
Source: docs.expo.dev/versions. Verified September 13, 2026.
npx react-native --version does not print the React Native version. It prints the version of the React Native CLI package, @react-native-community/cli, which is numbered separately (its latest release is 20.2.0). The CLI's own source passes its package.json version to --version.
To see the framework version actually installed:
npx react-native info lists the installed react, react-native, and @react-native-community/cli versions under npmPackages.npm ls react-native (or yarn why react-native) shows the installed version and anything else that pulls it in.node -p "require('react-native/package.json').version" prints just the version, run from the project folder.The react-native line in package.json is the version range you asked for, such as ^0.86.0, not necessarily what is installed. Your lockfile records the installed version. For Expo projects, the major version of the installed expo package is the SDK version, and the table above gives the React Native version it targets.
Sources: CLI source, react-native info source.
The free scanner reads your package-lock.json or yarn.lock and shows your installed React Native version, your Expo package version (if any), and which installed package versions have published security advisories.
Stuck on an upgrade? We fix broken React Native builds and run major-version upgrades at fixed price. See how it works →
The latest stable release on npm is 0.87.1, verified September 13, 2026. The React Native team lists 0.87 and 0.86 as Active and 0.85 as End of Cycle; older versions are Unsupported.
Recent minors have shipped about every two months. The official schedule on reactnative.dev lists 0.88 for October 12, 2026. Schedules can move.
No. The official policy is to maintain the latest 3 minor series: Active versions get frequent patches, the End of Cycle version gets fewer, and Unsupported versions should not expect new releases.
Each Expo SDK targets a single React Native version, so upgrading the SDK upgrades React Native. The newest SDK can lag the newest React Native: Expo SDK 57 targets React Native 0.86.
No new React Native releases are expected for it, so fixes land only in newer versions. In practice, newer libraries, Expo SDKs, and platform tooling also move on, which makes each later upgrade bigger. Versions before 0.82 can still run the Legacy Architecture, so upgrading them usually includes a New Architecture migration.
Run npx react-native info or npm ls react-native in the project. Do not use npx react-native --version: it prints the version of the React Native CLI package, which is numbered separately. The react-native entry in package.json is a requested range, and your lockfile has the installed version.
Staying within the Active versions keeps you on patched releases. Our own practice is to wait for the first patch release of a new minor and for key libraries to declare support before upgrading production apps. That is our recommendation, not an official policy.
It depends on how far behind you are, how many native modules you use, and whether the upgrade crosses the New Architecture boundary at 0.82. In our experience, one minor is often days of work and several minors is a multi-week project. Full upgrade playbook here.
Versions and statuses above were last verified September 13, 2026. Or let us check your app for you.
Run Free Scan →