From: Petr Špaček Date: Tue, 5 May 2026 13:04:36 +0000 (+0200) Subject: Mark merged security fixes as "Not released yet" X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bf0b49a6994e7a1de14182ff1cd0b936db0c9ae7;p=thirdparty%2Fbind9.git 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) --- diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index ee6ad205075..86fe0790b7d 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2635,7 +2635,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"