Question RE drupal Composer and Drupal Recommended

Created on 2 January 2025, 20 days ago

Problem/Motivation

I have DRUSH apparently locked at 13.0.0.0-beta1.

When I issue the command...

composer validate

I see...

require.chi-teck/drupal-code-generator : exact version constraints (3.5.0) should be avoided if the package follows semantic versioning

A subsequent...

composer depends chi-teck/drupal-code-generator

Reveals...

drupal/recommended-project dev-main     requires chi-teck/drupal-code-generator (3.5.0)
drush/drush                13.0.0-beta1 requires chi-teck/drupal-code-generator (^3 || 4.x-dev)

Does that mean that I am somehow using drupal/recommended-project in the dev flavour instead of the stable release?

Can anyone advise as to how to fix this up so that:

  1. I can update DRUSH
  2. I am firmly attached to the stable release of drupal/recommended-project if indeed I am not?

Thanks all

💬 Support request
Status

Active

Version

10.4

Component

composer

Created by

🇬🇧United Kingdom SirClickALot Somerset

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @SirClickALot
  • 🇮🇳India mdsohaib4242

    You can confirm that if you are using a development version by running this command

    composer show drupal/recommended-project
    

    If you see dev-main, it confirms that you are using a development version.

    To switch to a stable release, run:

    composer require drupal/recommended-project:^10.1 --no-update
    
    composer update
    

    Then you need to update your composer.json to allow a broader range for chi-teck/drupal-code-generator:

    composer require chi-teck/drupal-code-generator:^3.5 || ^4.0 --no-update
    

    Then update Drush to the latest stable version:

    composer require drush/drush:^12 --no-update
    
  • 🇬🇧United Kingdom SirClickALot Somerset

    Hi @mdsohaib4242,

    Thank you very much for the response.

    All sorted now I think after following tour guidance.

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

Production build 0.71.5 2024