Support Policy
The React Native for Windows (RNW) Team strives to provide full support for the latest stable version of RNW, with progressively reduced support for older released versions.
Support Matrix
| Version | Support Phase | Release Date | Active Support Start | Maintenance Support Start | End of Support |
|---|---|---|---|---|---|
| main | Canary | N/A | N/A | N/A | N/A |
| 0.76 | Active | 11/11/2024 | 11/11/2024 | TBD | TBD |
| 0.75 | Active | 8/19/2024 | 8/19/2024 | 12/31/2024 | 02/28/2025 |
| 0.74 | Unsupported | 4/29/2024 | 4/29/2024 | 9/30/2024 | 11/30/2024 |
| 0.73 | Unsupported | 12/11/2023 | 12/11/2023 | 5/31/2024 | 7/31/2024 |
| 0.72 | Unsupported | 06/23/2023 | 06/23/2023 | 01/31/2024 | 03/31/2024 |
| 0.71 | Unsupported | 01/23/2023 | 01/23/2023 | 07/31/2023 | 09/30/2023 |
Note: All releases not listed above are Unsupported.
Summary
RNW stable versions are referred to by their major and minor version number, e.g. 0.64, mapping to the same React Native stable version, and are sourced from an equivalently named *-stable branch in the RNW repo, e.g. 0.64-stable.
A new stable version's life begins when that stable branch is created and a package published to NPM under the preview tag. That version is said to be in preview and has entered Preview Support. After the preview period ends, the stable version becomes the new "latest" release and its package is published to NPM under the latest tag. That version has now entered Active Support.
At this point, the previous latest stable version is now considered a "legacy" version. Such legacy versions will receive progressively reduced support over time, specifically:
- One final month of Active Support, followed by
- Two months of Maintenance Support
After which, the legacy version will become Unsupported.
See below for further details on each support phase. For further details on the release process, see RNW Versioning and Release Process.
Support Phases
Active Support
A stable version of RNW enters Active Support status as soon as the first official, non-preview, package of that stable version is published to NPM. This support continues with each patch release within that stable version.
It is expected that the stable release branch is "stable" and will not take breaking API or project template changes (relative to the first official release in that branch).
While in Active Support, the RNW Team strives to provide support for this stable version by taking fixes¹ which resolve:
- Security and/or legal issues, e.g.:
- RNW, or one of its dependencies, has a known vulnerability
- RNW is consuming a dependency with an incompatible license
- Build and/or tooling issues², e.g.:
- RNW itself does not build
- A RNW app does not build with the
npx react-native run-windowsCLI command - A new RNW app cannot be created with the
npx react-native-windows-initCLI command
- Critical and/or important functional issues, e.g.:
- Unexpected crashes in RNW code
- A core RN component does not load
Active Support for a stable version ends one month after the release of the next stable version, at which point the previous stable version enters Maintenance Support.
Customers are encouraged to use versions receiving Active Support as much as possible.
¹: The RNW team reserves the right to triage reported issues and release fixes at their discretion.
²: Assuming the use of the supported development environment for that stable version at the time of its release.
Maintenance Support
A stable version of RNW enters Maintenance Support status one month after the next stable version is released. This support continues with each patch release within that stable version.
It is expected that the stable release branch is "stable" and will not take breaking API or project template changes (relative to the first official patch release in the branch).
While in Maintenance Support, the RNW Team strives to provide support for this stable version by taking fixes¹ which resolve:
- Security and/or legal issues (see examples above)
- Build and/or tooling issues² (see examples above)
Maintenance Support for a stable version lasts for two months after it leaves Active Support, after which the stable version will be considered Unsupported.
Customers are encouraged to upgrade away from versions receiving Maintenance Support as soon as possible.
¹: The RNW team reserves the right to triage reported issues and release fixes at their discretion.
²: Assuming the use of the supported development environment for that stable version at the time of its release.
Canary Support
Canary builds/releases are in active development and are not meant for general consumption.
It is expected that the main release branch is "unstable" and can take breaking changes.
The RNW Team does not commit to any support for these releases.
Customers should not use canary versions.
Preview Support
A stable version of RNW enters Preview Support as soon as the first preview package is published on NPM. This support continues with each patch preview release within that stable version.
It is expected that the stable release branch in preview is "stabilizing," and it is the last chance to make large and/or breaking changes to that branch.
While in Preview Support, the RNW Team strives to provide this stable version the equivalent of Active Support, but breaking API and/or template changes may be allowed.
Preview Support for a stable version ends as soon as the first official, non-preview, package of the stable version is published to NPM, at which point it enters Active Support.
Unsupported
An Unsupported stable version of RNW should not expect any further updates, changes, or fixes.
The RNW Team does not commit to any support for these releases.
Customers are encouraged to upgrade away from Unsupported versions as soon as possible.
React Native Support Policy
See the official React Native Support Policy.