Problem/Motivation

Drupal CMS site templates are installed on projects that resolve with Composer's default minimum-stability: stable. Varbase Starter cannot:

composer require drupal/varbase_starter:~1.0.0

  - drupal/varbase_admin_base 1.0.0 requires drupal/entity_clone ~2 -> found drupal/entity_clone[2.0.0-alpha1, ..., 2.2.0-beta1] but it does not match your minimum-stability.

Ten contrib packages required through the base recipes have no stable release that satisfies the constraint. Six of them arrive through four recipes that this template requires in composer.json but never applies:

  • drupal/varbase_ai_base brings ai_integration_eca
  • drupal/varbase_api_base brings openapi_ui_redoc
  • drupal/varbase_auth_base brings social_api and social_auth
  • drupal/varbase_i18n_base brings canvas_translate and ai_tmgmt

None of the four appears in the recipes: list in recipe.yml, so nothing installs them. They add weight to every site built from this template and block a stable install, for no functional gain.

Steps to reproduce

  1. On a project with the default minimum-stability: stable, run composer require drupal/varbase_starter:~1.0.0.
  2. Resolution fails on a dependency with no stable release.
  3. Compare the require block in composer.json with the recipes: list in recipe.yml. Fourteen of the eighteen required base recipes are applied; four are not.

Proposed resolution

Remove the four never-applied recipes from composer.json:

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

They move to the drupal/varbase_project template, whose root composer.json sets minimum-stability: dev and can carry them. A site that wants AI, API, authentication or multilingual features applies those recipes there.

No change to recipe.yml, and no change to what the template installs.

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ✅ Testing to ensure no regression
  • ✅ Reviewed by a human
  • ✅ Code review by maintainers
  • ✅ Release varbase_starter-1.0.1

User interface changes

  • None.

API changes

  • Four packages are no longer required by this template. A site relying on them getting installed as a side effect must require them itself, or use drupal/varbase_project.

Data model changes

  • None.

Release notes snippet

  • Remove the four base recipes the template required but never applied, so it resolves on a project with the default stable stability.
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Title: Remove the four never-applied base recipes so the template resolves on stable » Varbase Starter: remove the four never-applied base recipes to resolve on Stable for Drupal CMS
rajab natshah’s picture

Title: Varbase Starter: remove the four never-applied base recipes to resolve on Stable for Drupal CMS » Remove the four never-applied base recipes from Varbase Starter to resolve on Stable for Drupal CMS
rajab natshah’s picture

Issue tags: -varbase-11.0

  • rajab natshah committed 5fd56916 on 1.0.x
    fix: #3621334 Remove the four never-applied base recipes from Varbase...
rajab natshah’s picture

Status: Active » Needs review
rajab natshah’s picture

Assigned: rajab natshah » Unassigned
Issue summary: View changes
Status: Needs review » Fixed
Issue tags: +varbase_starter-1.0.1

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.