task: #3621338 Stop requiring the base recipes that vardot/varbase already requires

Rajab Natshahrequested to merge
issue/varbase_project-3621338:3621338-drop-duplicated-base-recipes into 11.0.x

Issue: #3621338

Follow-up on the same issue. That issue moved the AI, API, authentication and multilingual base recipes into Varbase Project when the four site templates dropped them. They now live in the vardot/varbase profile (#3621480), which Varbase Project requires, so the copies here are redundant.

What changed

composer.json: removed every drupal/varbase_* requirement.

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

All five now arrive through vardot/varbase. Nothing changes about what is installed.

varbase_dev_base was the one the profile did not carry, so it is added there first in varbase !83. Merge that before this, or a Varbase Project site loses it.

Verified on the branch: no drupal/varbase_* entries remain, and vardot/varbase is still required at 11.0.x-dev.

Why bother

Two constraints for one package in the same tree is a maintenance trap. At the next version bump one gets updated and the other quietly does not, and the tighter of the two silently wins. One home for the varbase_* set removes that whole class of drift.

Checkpoints

  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Reviewed by a human
  • Code review by maintainers
  • Release

This work was done with the help of AI, and reviewed by a human. Per the Drupal AI policy.

Edited by Rajab Natshah

Merge request reports