Problem/Motivation

The project ships no top-level info file, so drupal.org's composer facade publishes it with no dependencies: composer require drupal/cucumber_demos:12.0.0 installs nothing else and drush en cucumber_demo_small fails with "missing its dependency module cucumber_projects". Separately, the demo recipes fail on a fresh site with "Field moderation_state is unknown": the covering workflow is a config entity that a recipe install skips.

Steps to reproduce

On a fresh Drupal 11.4.7 + PHP 8.4 site with assertions on: composer require drupal/cucumber_demos:12.0.0, then drush en cucumber_demo_small.

Proposed resolution

Add a hidden packaging anchor info file, as done for cucumber_recipes. Have the small and medium recipes import workflows.workflow.automated_testing so the workflow config entity exists before content is created.

Remaining tasks

  • ✅ 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

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
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 dbdc0ce4 on 12.0.x
    fix: #3625319 Publish the package dependencies and apply the demo...
rajab natshah’s picture

Status: Active » Fixed
Issue tags: +cucumber_demos-12.0.1

✅ Released in cucumber_demos 12.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.