fix: #3621094 Declare a version for the path repository in the functional testing jobs

Rajab Natshahrequested to merge
issue/varbase_ai_figma-3616971:3621094-path-repo-version into 1.0.x

The functional-testing jobs cannot resolve dependencies, so both legs fail before a single test runs.

Issue: https://www.drupal.org/i/3621094

Problem

The module under test is installed from a Composer path repository. A path repo is canonical and outranks packages.drupal.org, so the version it declares is the only version of this module Composer can see. It declared none, so the module was offered as dev-<sha>.

drupal/varbase_ai_figma_base has back-pinned drupal/varbase_ai_figma:~1.0.0 since its 1.0.0-rc2 (16 Aug 2026) — the day after this project's last green 1.0.x pipeline (924431, 15 Aug). dev-<sha> satisfies no ~1.0.x constraint, so resolution dies:

- drupal/varbase_ai_figma_base 1.0.0-rc2 requires drupal/varbase_ai_figma ~1.0.0
  -> ... but drupal/varbase_ai_figma[dev-3cc6862...] from path repo has higher
     repository priority. The packages from the higher priority repository do not
     match your constraint and are therefore not installable.

This is not fixed by tagging a stable release: the path repo keeps shadowing the released tag on every future MR.

Resolution

Declare the path repository's version, derived from the branch rather than hardcoded, so it does not go stale when the branch moves to 1.1.x:

Pipeline Value
MR into 1.0.x 1.0.x-dev
Branch 1.0.x / 1.1.x 1.0.x-dev / 1.1.x-dev
Tag 1.0.0 1.0.0

Verified against composer/semver directly:

  • dev-<sha> satisfies ~1.0.0: no (the bug)
  • 1.0.x-dev normalises to 1.0.9999999.9999999-dev, satisfies ~1.0.0: yes, stability dev, which this build allows (minimum-stability: dev)
  • 1.1.x-dev satisfies ~1.1.0: yes (so the derived form self-maintains)

One edit covers both functional-testing legs: functional-testing (Varbase) and functional-testing (AI live agent - amazee.ai) both extends: .functional-testing and share its single before_script.

Remaining tasks

The full pipeline on this MR is the test — functional-testing (Varbase) going green is the point of the change. gitlab-ci-local cannot run this project's pipeline (drupal/gitlab_templates trips firecow/gitlab-ci-local#1893), so the remote pipeline is the gate.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release

Merge request reports