Freshly installed drupal-cms using composer create-project. system states updates are needed. going in to admin->extend and then clicking on update i get the following error:
Error message
Warning: Undefined array key "project_status" in Drupal\package_manager\ProjectInfo->getInstallableReleases() (line 96 of core/modules/package_manager/src/ProjectInfo.php).
Warning: Undefined array key "project_status" in Drupal\package_manager\ProjectInfo->getInstallableReleases() (line 97 of core/modules/package_manager/src/ProjectInfo.php).
The project 'drupal' can not be updated because its status is
it never says what the status is as shown. I have also included the latest error log from the apache log.
i am running this on the computer for design purposes for a potential site redesign including new software.
computer system specs as follow:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.11-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 16 GiB of RAM (13.5 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82SG
System Version: IdeaPad 5 15ABA7
| Comment | File | Size | Author |
|---|---|---|---|
| error_log-20251221.txt | 13.59 KB | efwis |
Comments
Comment #2
efwis commentedComment #3
cilefen commentedPackage manager is an experimental module. I didn’t know CMS enables it.
Can we see the complete
composer create-projectcommand you typed and its complete output?Are you using DDEV as recommended for development or a custom web server configuration?
Comment #4
dwwDrupal CMS enables automatic_updates (from contrib) by default. That's what's injecting the 'update' link on admin/extend. Tempted to move this issue over there, but sure, we can call it a package_manager.module bug for now. Regardless, update.module (Update Status) is not involved here, so thanks for moving the component.
Comment #5
laborheld commentedI’m experiencing the same issue. I’ve documented the root cause here: https://www.drupal.org/project/drupalorg/issues/3564827
The problem appears to be that the API endpoint `https://updates.drupal.org/release-history/drupal/current` is returning ‘No release history’ errors, which causes the `project_status` array key to be undefined in `ProjectInfo->getInstallableReleases()`.
This seems to be a recurrence of issue #3470260, which was marked as fixed in August 2024.[drupal]
I guess we’ll need to wait for the Drupal.org infrastructure team to investigate? Any workarounds or solutions would be greatly appreciated.
Comment #6
cilefen commentedComment #8
dwwAlthough the infra problem is resolved, I think it’s a major bug that package_manager will fatal error in this situation instead of gracefully providing an error that callers (in this case, automatic_updates) can notice and provide useful feedback.
Comment #9
cilefen commentedThe issue title and summary need updating with information from comment 5 or this will languish.
Comment #10
quietone commented