From a168911ef02837fa07946b90aa8d0eedb9c60eb8 Mon Sep 17 00:00:00 2001 From: Noah Biewesch Date: Fri, 5 Jun 2026 19:01:14 +0200 Subject: [PATCH] doc/src/backport_policy: add maintainer changes to backport criteria (#2344) Add maintainer changes to the backport criteria to remove ambiguity about whether they are included in the existing CI condition. Maintainer changes should be backported to keep maintainer notifications in sync between the unstable and stable branches. Link: https://github.com/nix-community/stylix/pull/2344 Reviewed-by: 0xda157 --- doc/src/backport_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/backport_policy.md b/doc/src/backport_policy.md index d379e9cb..43bfcf4b 100644 --- a/doc/src/backport_policy.md +++ b/doc/src/backport_policy.md @@ -6,7 +6,7 @@ applied to the current stable (`release-*.*`) branch. To reduce maintenance efforts and improve stability on stable branches, security fixes, bug fixes, and CI changes are backported, while new features, modules, and theme improvements are not backported. Upstream changes causing theming -issues are considered a bug. +issues are considered a bug and maintainer changes are considered as CI changes. New modules and theme improvements may be backported when explicitly requested and backporting is trivial.