From 805beb13e5d7b90663e57ba0f7cb18ccd4629cdc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0pa=C4=8Dek?= Date: Tue, 5 May 2026 15:04:36 +0200 Subject: [PATCH] Mark merged security fixes as "Not released yet" Adjust the triggering rules for the "merged-metadata" CI job so that merge requests merged into security-* branches are automatically assigned to the "Not released yet" milestone, just like merge requests targeting public branches. This enables merge requests containing security fixes to be correctly processed by release automation scripts. (cherry picked from commit afdf7bed602b5518b23409c1a140a797c4e6de34) --- .gitlab-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index bc5568164b..7020df67c3 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2429,7 +2429,7 @@ backports: merged-metadata: <<: *post_merge rules: - - if: '$CI_PIPELINE_SOURCE == "push" && ($CI_COMMIT_REF_NAME =~ /^bind-9.[0-9]+(-sub)?$/ || $CI_COMMIT_REF_NAME =~ /^v9.[0-9]+.[0-9]+-release$/ || $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH)' + - if: '$CI_PIPELINE_SOURCE == "push" && ($CI_COMMIT_REF_NAME =~ /^security-(main|bind-9\.[0-9]+)$/ || $CI_COMMIT_REF_NAME =~ /^bind-9.[0-9]+(-sub)?$/ || $CI_COMMIT_REF_NAME =~ /^v9.[0-9]+.[0-9]+-release$/ || $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH)' script: - > "$CI_PROJECT_DIR"/bind9-qa/releng/after_merge.py "$CI_PROJECT_ID" "$MERGE_REQUEST_ID"