Attempting an update from 10.0.9 to 10.1.0 ignores drupal/core-recommended or drupal/core, however does successfully update drupal/core-composer-scaffold and drupal/core-project-message, among other modules.
On a development site running 10.0.9 (upgraded from 9.5.9 using the less recommended approach here → (leaving a drupal/core ^10.0.0 entry in composer.json), I run the command:
composer update "drupal/core-*" --with-all-dependencies --dry-run
Results in the following output:
Problem 1
drupal/upgrade_status is locked to version 4.0.0 and an update of this package was not requested.
Removal of the upgrade_status module, I re-ran the update command, I expecting a dry-run update to Drupal core and dependencies. Instead, core is ignored. See below output:
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 15 updates, 1 removal
- Removing brick/varexporter (0.3.8)
- Upgrading doctrine/deprecations (v1.0.0 => v1.1.1)
- Upgrading drupal/ckeditor (1.0.1 => 1.0.2)
- Upgrading drupal/core-composer-scaffold (10.0.9 => 10.1.0)
- Upgrading drupal/core-project-message (10.0.9 => 10.1.0)
- Upgrading egulias/email-validator (3.2.5 => 3.2.6)
- Downgrading laminas/laminas-servicemanager (3.21.x-dev 1478587 => 3.15.0)
- Upgrading symfony/console (v6.2.11 => v6.2.12)
- Upgrading symfony/dependency-injection (v6.2.11 => v6.2.12)
- Upgrading symfony/http-foundation (v6.2.11 => v6.2.12)
- Upgrading symfony/http-kernel (v6.2.11 => v6.2.12)
- Upgrading symfony/property-info (v6.2.11 => v6.3.0)
- Upgrading symfony/routing (v6.2.8 => v6.2.12)
- Upgrading symfony/serializer (v6.2.11 => v6.2.12)
- Upgrading symfony/validator (v6.2.11 => v6.2.12)
- Upgrading symfony/var-dumper (v6.2.11 => v6.2.12)
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 15 updates, 1 removal
- Removing brick/varexporter (0.3.8)
- Upgrading drupal/core-composer-scaffold (10.0.9 => 10.1.0)
- Upgrading drupal/core-project-message (10.0.9 => 10.1.0)
- Upgrading symfony/console (v6.2.11 => v6.2.12)
- Upgrading doctrine/deprecations (v1.0.0 => v1.1.1)
- Upgrading symfony/validator (v6.2.11 => v6.2.12)
- Upgrading symfony/serializer (v6.2.11 => v6.2.12)
- Upgrading symfony/routing (v6.2.8 => v6.2.12)
- Upgrading symfony/http-foundation (v6.2.11 => v6.2.12)
- Upgrading symfony/var-dumper (v6.2.11 => v6.2.12)
- Upgrading symfony/http-kernel (v6.2.11 => v6.2.12)
- Upgrading symfony/dependency-injection (v6.2.11 => v6.2.12)
- Upgrading egulias/email-validator (3.2.5 => 3.2.6)
- Upgrading drupal/ckeditor (1.0.1 => 1.0.2)
- Downgrading laminas/laminas-servicemanager (3.21.x-dev 1478587 => 3.15.0)
- Upgrading symfony/property-info (v6.2.11 => v6.3.0)
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
57 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories foundRelevant lines in composer.json:
"drupal/core": "^10.0.0",
"drupal/core-composer-scaffold": "^10",
"drupal/core-project-message": "^10",
"drupal/core-recommended": "^10",Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Show the output of: 'composer why-not drupal/core:10.1.0' and provide us the composer.json file.
Here is the sub command documentation https://getcomposer.org/doc/03-cli.md#prohibits-why-not.
This is not a bug.