-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update SECURITY.md and remove support for 2.x version #4683
Conversation
|
@@ -30,13 +30,14 @@ Only critical severity bug fixes will be backported to past major releases. | |||
|
|||
| Version | Critical security fixes | Other security fixes | | |||
| ------- | ----------------------- | -------------------- | | |||
| 4.x | :white_check_mark: | :white_check_mark: | | |||
| 5.x | :white_check_mark: | :white_check_mark: | | |||
| 4.9 | :white_check_mark: | :x: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you agree with this? @Amxx
We probably would like to keep medium severity fixes in 4.9 along with the critical for some time.
Co-authored-by: Eric Lau <[email protected]>
The community keeps referencing the security page and we should communicate correctly what are we supporting. I'm merging. |
With the new 5.x release, we can remove security fixes support for versions like 2.x
Also, adds support for 5.x release and it'll show up in the Security Policy once merged.
PR Checklist
npx changeset add
)