From 90f3aa450fef97dd2520f1fde58225ddfa4baaa9 Mon Sep 17 00:00:00 2001 From: Sebastian Wick Date: Mon, 8 Jun 2026 14:32:34 +0200 Subject: [PATCH] Update SECURITY.md --- SECURITY.md | 8 ++++---- doc/release-checklist.md | 3 +++ 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index a4d861e0d..e275e2987 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -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 diff --git a/doc/release-checklist.md b/doc/release-checklist.md index 2747f9d71..07ec428a6 100644 --- a/doc/release-checklist.md +++ b/doc/release-checklist.md @@ -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