fix(pages): branch rule compares variables, not a quoted literal

Andrew Dunnrequested to merge
fix/pages-branch-rule into main

What

The pages component's deploy rule interpolated the branch input inside quotes:

rules:
  - if: $CI_COMMIT_BRANCH == "$[[ inputs.branch ]]"

GitLab rules:if treats a quoted right side as a literal string. With the default input ($CI_DEFAULT_BRANCH) the rendered rule compares the branch name against the literal text $CI_DEFAULT_BRANCH, which never matches, and the pages job silently drops from every consumer pipeline that uses defaults.

How it surfaced

The egress project's first catalog-based pipeline ran only its check jobs; the merged YAML showed the pages job present with a rule that could never match. Consumer-side workaround (pinning branch: "main" as a literal) is in place there and can be reverted once this releases.

Fix

The input lands in a job variable and the rule compares variable to variable, which works for both the variable default and an explicit literal branch:

variables:
  PAGES_DEPLOY_BRANCH: '$[[ inputs.branch ]]'
rules:
  - if: $CI_COMMIT_BRANCH == $PAGES_DEPLOY_BRANCH

Swept the other component templates for the same quoted-input-in-rules shape: pages is the only one.

Release note

Needs a patch release (v4.1.1) to reach consumers; tagging left to the maintainer.

🤖 Generated with Claude Code

Merge request reports