Skip to content

Commit

Permalink
Clarify security updates in versioning-policy.md (#7485)
Browse files Browse the repository at this point in the history
  • Loading branch information
sophiebits authored Feb 9, 2025
1 parent 6fc98ff commit 91614a5
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions src/content/community/versioning-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ All stable builds of React go through a high level of testing and follow semanti

</Intro>

For a list of previous releases, see the [Versions](/versions) page.
This versioning policy describes our approach to version numbers for packages such as `react` and `react-dom`. For a list of previous releases, see the [Versions](/versions) page.

## Stable releases {/*stable-releases*/}

Expand All @@ -24,7 +24,9 @@ Major releases can also contain new features, and any release can include bug fi

Minor releases are the most common type of release.

### Breaking Changes {/*breaking-changes*/}
We know our users continue to use old versions of React in production. If we learn of a security vulnerability in React, we release a backported fix for all major versions that are affected by the vulnerability.

### Breaking changes {/*breaking-changes*/}

Breaking changes are inconvenient for everyone, so we try to minimize the number of major releases – for example, React 15 was released in April 2016 and React 16 was released in September 2017, and React 17 was released in October 2020.

Expand Down

0 comments on commit 91614a5

Please sign in to comment.