Problem/Motivation

drupal/entity_clone has no stable release. 2.x is beta only, so any project resolving with Composer's default minimum-stability: stable cannot install a recipe that requires it:

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

That blocks the Varbase site templates from being installed on Drupal CMS, where a site template has to resolve on stable. Entity Clone is required by three Varbase base recipes, so it blocks all of them: this one, Varbase Content Base and Varbase SEO Base.

We asked the maintainers for a stable 2.x tag in #3189738.

This removal is temporary. When Entity Clone 2.x has a stable release, it goes back.

Steps to reproduce

  1. On a project with the default minimum-stability: stable, run composer require drupal/varbase_admin_base:~1.0.0.
  2. Resolution fails on drupal/entity_clone.

Proposed resolution

Remove drupal/entity_clone from composer.json, and remove entity_clone from the install: list in recipe.yml.

Sites already running the module keep it enabled; Composer simply stops requiring it. Worth a release note so a site owner who wants entity cloning knows to require it themselves.

A longer-term option is a clone workflow built on ECA, which Varbase already ships: eca_content provides an Entity: clone existing action. It performs a shallow createDuplicate() and does not follow referenced entities or translations, so it needs prototyping before it could replace the module.

Remaining tasks

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

User interface changes

  • On a new site the Entity Clone tab and its clone action are no longer present, because the module is no longer installed by this recipe.

API changes

  • drupal/entity_clone is no longer required by this recipe.

Data model changes

  • None.

Release notes snippet

  • Temporarily stop requiring and installing Entity Clone, which has no stable release, so the recipe resolves on a project with the default stable stability. It returns when #3189738 ships a stable 2.x.
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 committed 7033d97c on 1.0.x
    task: #3621449 Temporarily remove Entity Clone until it has a stable...
rajab natshah’s picture

Assigned: rajab natshah » josebc
Status: Active » Needs review
rajab natshah’s picture

Assigned: josebc » Unassigned
Issue summary: View changes
Status: Needs review » Fixed

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.

rajab natshah’s picture

Issue summary: View changes
Issue tags: +varbase_admin_base-1.0.1

Status: Fixed » Closed (fixed)

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