DRUPAL_CORE not taken into account

Issue information

From user: grimreaper

Related to !269 (merged)

Contribution record

Fork management

Problem/Motivation

In MR https://git.drupalcode.org/project/sobki_profile_bootstrap/-/merge_requests/20, I got the job https://git.drupalcode.org/project/sobki_profile_bootstrap/-/jobs/3016726 showing me that "_TARGET_CORE" is deprecated.

After switching to DRUPAL_CORE, in the new pipeline I got https://git.drupalcode.org/project/sobki_profile_bootstrap/-/jobs/3017065

Root composer.json requires drupal/core-composer-scaffold 10.3.6 (exact version match: 10.3.6 or 10.3.6.0), found drupal/core-composer-scaffold[10.3.x-dev] but it does not match the constraint.

I think it should be dynamically obtained from DRUPAl_CORE and/or the composer.json of the project in scripts/expand_composer_json.php?

I wonder if I should add IGNORE_PROJECT_DRUPAL_CORE_VERSION: 0 in my variables but I thought it would had been taken into account automatically.

Is it a side effect, or something forgotten from #3478044: Find a better consistent way to override the core version?

Thanks for any help.

Proposed resolution

Remaining tasks

Edited by drupalbot
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information