Norman

Maybe something like `DRUPAL-CONCAT.PROJECT.PROJECT`? * `859.0.0` * `859.1.0` * `860.0.0` * `861.0.0` * etc. Although that would mean much more tagging. And probably fixating the Drupal version in the `composer.json`....

Or would fixating the Drupal version for every release be a desired thing? > This would also be useful if you want to download an older version to test upgrading.

On the other hand. Starting with just `1.0.0` should be fine for drupal-project, no? Confusion with Drupal versions should be minimal as long as drupal-project doesn't make big jumps too...

👍 Nice to have, yes. But environment is totally up to every developer themself and goes beyond the scope of this template I guess.

This feature request sounds a bit out-of-scope to me since there are like hundreds of CI SaaS out there and every tool seems to do it differently.

Whoop whoop, seems a D9 compatible release has been tied up: https://github.com/hechoendrupal/drupal-console/releases/tag/1.9.5

Sorry for the late reply. Do you maybe have a sample Drush package at hand to reproduce that? This would help a lot. Many thanks!

Sounds good. You can simply adjust the ScriptHandler.php in your project.

Core 8 composer.json has [`"php": "^7.0.8"`](https://git.drupalcode.org/project/drupal/-/blob/8.9.12/core/composer.json#L20) and core 9 composer.json has [`"php": ">=7.3.0"`](https://git.drupalcode.org/project/drupal/-/blob/9.1.2/core/composer.json#L20) already. So I guess that should already be enough actually. We could move the PHP requirement to...

What's DCG?