fix: #3621334 Remove the four never-applied base recipes from Varbase Starter to resolve on Stable for Drupal CMS

Rajab Natshahrequested to merge
issue/varbase_starter-3621334:3621334-remove-the-four into 1.0.x

Closes #3621334.

Why

These base recipes are required in composer.json but never listed in this template's recipe.yml, so they are pulled in as dependencies and never applied. They bring contrib packages that have no stable release, which blocks installing the template on a project using Composer's default minimum-stability: stable. Removing them changes nothing about what the template installs; only the dependency tree is cleaned. They are added to drupal/varbase_project in #3621338, whose root sets minimum-stability: dev.

What changed

Removed from require in composer.json:

  • drupal/varbase_ai_base
  • drupal/varbase_api_base
  • drupal/varbase_auth_base
  • drupal/varbase_i18n_base

.gitlab-ci.yml is also touched, in a second commit. This project's Varbase install job already states the intent our composer.json change now matches:

# The copied varbase_project suites exercise the API / Auth / i18n / AI
# stacks, which the Varbase Starter recipe deliberately does not compose.
# Pull those recipe packages into the TEST HOST (the Starter recipe itself
# is unchanged) so the `dr recipe` applies below find them. on-require must
# be false or core-recipe-unpack unpacks each recipe into the root
# composer.json and removes the package, leaving recipes/<name> absent.

The Starter recipe was already designed not to compose these; the composer.json entries were the anomaly.

The Drupal CMS install job had no such extra require, so with the four packages gone from composer.json its front-end library assertion failed on web/libraries/swagger-ui/dist/swagger-ui-bundle.js and swagger-ui.css, which come from openapi_ui_swagger via drupal/varbase_api_base. Rather than weaken the assertion, that job now pulls the four recipe packages into its test host too, after requiring the recipe under test and before the assertion. The assertion is unchanged, and the four recipes stay under test.

composer.json and .gitlab-ci.yml are the only two files touched. recipe.yml, config, content and tests are unchanged; the JSON and the YAML were both parsed after editing to confirm they still load.

AI policy disclosure

AI-Generated: Yes

Checkpoints

  • File an issue about this project
  • Addition/Change/Update/Fix to this project
  • Testing to ensure no regression
  • Automated unit/functional testing coverage
  • Developer Documentation support on feature change/addition
  • User Guide Documentation support on feature change/addition
  • UX/UI designer responsibilities
  • Accessibility and Readability
  • Reviewed by a human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Update Release Notes
  • Release
Edited by Rajab Natshah

Merge request reports