mirror of
https://github.com/flatpak/flatpak.git
synced 2026-06-26 01:06:57 -04:00
Update SECURITY.md
This commit is contained in:
@@ -13,11 +13,11 @@ please check
|
||||
|
||||
| Version | Supported | Status
|
||||
| -------- | ------------------ | -------------------------------------------------------------- |
|
||||
| 1.17.x | :hammer: | Development branch, releases may include non-security changes |
|
||||
| 1.16.x | :white_check_mark: | Stable branch, recommended for use in distributions |
|
||||
| ≤ 1.15.x | :x: | Older branches, no longer supported |
|
||||
| 1.19.x | :hammer: | Development branch, releases may include non-security changes |
|
||||
| 1.18.x | :white_check_mark: | Stable branch, recommended for use in distributions |
|
||||
| ≤ 1.17.x | :x: | Older branches, no longer supported |
|
||||
|
||||
The latest stable branch (currently 1.16.x) is the highest priority for
|
||||
The latest stable branch (currently 1.18.x) is the highest priority for
|
||||
security fixes.
|
||||
If a security vulnerability is reported under embargo, having new releases
|
||||
for older stable branches will not always be treated as a blocker for
|
||||
|
||||
@@ -7,6 +7,9 @@ Flatpak release checklist
|
||||
* Commit the changes
|
||||
* `ninja -C ${builddir} flatpak-update-po`
|
||||
* This will update `po/`; commit those changes too
|
||||
* If this is the first release of a new stable release series, update
|
||||
`SECURITY.md`. It should list the development branch and new stable branch as
|
||||
currently maintained.
|
||||
* `git evtag sign $VERSION`
|
||||
* `git push --atomic origin main $VERSION`
|
||||
* Ensure the release.yml workflow succeeds
|
||||
|
||||
Reference in New Issue
Block a user