feat: #3621020 Add the Varbase Dev Base recipe to the Varbase Project Template composer.json

Rajab Natshahrequested to merge
issue/varbase_project-3621020:3621020-add-the-varbase into 11.0.x

Issue: https://www.drupal.org/project/varbase_project/issues/3621020 Pair issue: https://www.drupal.org/project/varbase_starter/issues/3621019

What changed

One line added to require in composer.json, between drupal/core and drush/drush so the entry stays in the existing alphabetical order of the block:

"drupal/varbase_dev_base": "~1.0.0",

require, not require-dev — this is the maintainer's explicit choice for the project template.

Why

The development stack belongs with the project template a site is created from, not inside the Varbase Starter site-template recipe, which never applies it (removed there in #3621019). Putting it here means a new Varbase project has the development recipe available from the first composer create-project.

Release notes

Every site created from the Varbase Project Template will ship devel, storybook, reroute_email, stage_file_proxy and devel_entity_updates in production unless the builder removes them. That is the honest consequence of requiring the recipe rather than dev-requiring it, and it matches what Varbase Dev Base's own description advises doing: remove it before going live.

Verification actually performed

  • composer.json still parses as valid JSON after the addition.
  • The branch is based on the current 11.0.x head, re-fetched immediately before branching.

To watch on the pipeline

Varbase Starter's .gitlab-ci.yml around line 493 records that drupal/storybook (pulled in via varbase_dev_base) conflicts with a locked symfony/css-selector on a partial update. Lock resolution on this pipeline is the thing to watch; a clean full resolve here does not by itself prove a partial update on an existing project will resolve.

NOT tested

  • composer.json edit only. No install and no lock regeneration were performed locally. Nothing here has been resolved by Composer outside CI.

AI policy

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
Edited by Rajab Natshah

Merge request reports