Problem/Motivation
Using Drupal 11.2.9, the Available updates section located at /admin/reports/updates warns me that Drupal 11.2.10 is available.
Performing a composer update -W command does the update:
user@server:~/public_html$ composer update -W
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 3 updates, 0 removals
- Upgrading drupal/core-composer-scaffold (11.2.9 => 11.2.10)
- Upgrading drupal/core-project-message (11.2.9 => 11.2.10)
- Upgrading drupal/core-recipe-unpack (11.2.9 => 11.2.10)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 3 updates, 0 removals
- Upgrading drupal/core-composer-scaffold (11.2.9 => 11.2.10): Extracting archive
- Upgrading drupal/core-project-message (11.2.9 => 11.2.10): Extracting archive
- Upgrading drupal/core-recipe-unpack (11.2.9 => 11.2.10): Extracting archive
Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
47 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
user@server:~/public_html$ cd web
user@server:~/public_html/web$ ../vendor/drush/drush/drush updb
[success] No pending updates.
After performing a drush updb command, Drupal 11.2.10 is supposed to be installed but this is not the case as shown in the image in attachment: Drupal 11.2.9 is still installed.
Steps to reproduce
composer update -W
drush updb
Proposed resolution
None
| Comment | File | Size | Author |
|---|---|---|---|
| Capture d’écran du 2025-12-10 13-25-20.png | 134.22 KB | gillesbailleux |
Comments
Comment #2
longwaveThis is likely an issue with your composer.json, please post the contents of that, or try
Comment #3
gillesbailleuxThank you dave for your quick answer and for the command line.
Here is what is displayed.
Comment #4
gillesbailleuxAfter performing the suggested command line
composer update "drupal/core:11.2.10" --dry-run, this is displayed:Comment #5
longwaveI guess you have
drupal/core-recommendedset to exactly11.2.9in your composer.json, instead of something like^11.2.9which will let you install newer versions.Comment #6
longwaveIf that's not the case try the dry run again with the
-Woption.Comment #7
gillesbailleuxHere is what is in the composer.json file:
"drupal/core-recommended": "^11.2"Comment #8
gillesbailleuxPerforming the
composer update -W "drupal/core:11.2.10" --dry-runcommand displays this:Comment #9
mitrpaka commentedAlso experiencing the very same:
And
composer update "drupal/core-*" --with-all-dependencieswon't help either (if run again)In composer.json having:
drupal/core-composer-scaffold,drupal/core-project-messageanddrupal/core-devupdated to11.2.10incomposer.lockfile butdrupal/core-recommendedanddrupal/coreremains11.2.9---
composer --version
Composer version 2.9.2 2025-11-19 21:57:25
Comment #10
longwaveWhat does
composer why-not drupal/core-recommended 11.2.10say?Also anything I say here is just guessing - the only way to reproduce exactly is with your full composer.json and .lock files.
Comment #11
gillesbailleuxComment #12
longwaveAhh, now that is interesting, we need someone at the Drupal Association to see why that's not in packagist...
Comment #13
cilefen commentedProvide the
composer.jsonfile for support.Comment #14
gillesbailleuxHere is the composer.json:
Comment #15
longwaveThe tag is there in the GitHub subtree split: https://github.com/drupal/core-recommended/tree/11.2.10
But it's not yet showing up in packagist: https://packagist.org/packages/drupal/core-recommended
Comment #16
cilefen commentedYes,
composer show -a drupal/core-recommendedconfirms that on the client side.Comment #17
cilefen commentedComment #18
longwaveThis should be fixed now; @drumm noticed that the webhook from GitHub to Packagist failed, but a manual redelivery means the 11.2.10 package is now showing up.
If someone can try the commands again and confirm it's fixed that would be helpful.
Comment #19
kmontyMy projects were having this issue earlier, but the issue is now resolved. We were able to successfully update our application to 11.2.10.
Comment #20
gillesbailleuxPerforming a
composer update -Wcommand folowed by adrush updbcommand installs gracefully Drupal 11.2.10.Thank you very much!
Comment #21
longwaveThanks for reporting back!
Comment #24
cilefen commented