Skip to content

Commit ea3395f

Browse files
authored
Update security policy in SECURITY.md
Clarified backporting policy for security fixes and emphasized the importance of using the latest stable release. Signed-off-by: Alex <inbox@alexv-pro.ru>
1 parent 7a0d537 commit ea3395f

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

‎SECURITY.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@ When only one stable minor release line exists, only that line is supported.
2020

2121
\* Vulnerability reports affecting a current pre-release version may still be accepted if the issue is relevant to an upcoming stable release. Pre-release builds are provided without any guarantee of stability or security support.
2222

23+
After a major version release, security fixes for supported release lines of the previous major version are backported on a best-effort basis, where technically feasible.
24+
25+
Backporting may be limited by the availability of upstream security fixes and continued support for required dependencies. If a backport is not feasible, upgrading to a newer major version may be required.
26+
2327
Security fixes are not guaranteed to be backported to unsupported versions.
2428

2529
Users are strongly encouraged to run the latest stable release.

0 commit comments

Comments
 (0)