The Update API endpoint https://updates.drupal.org/release-history/drupal/current is returning an error instead of the Drupal core release history. This causes the Update module and Package Manager module to fail when checking for Drupal core updates.
Error Response:
<?xml version="1.0" encoding="utf-8"?>
No release history was found for the requested project (drupal).
This appears to be the same issue that was reported and supposedly fixed in August 2024 (see #3470260).
Steps to Reproduce
Run: curl https://updates.drupal.org/release-history/drupal/current
Observe the error response instead of valid XML release data
Expected Behavior
The endpoint should return valid XML with Drupal core release information, similar to:
https://updates.drupal.org/release-history/drupal/all (works correctly)
https://updates.drupal.org/release-history/token/current (works correctly for contrib)
Actual Behavior
https://updates.drupal.org/release-history/drupal/current → Error
https://updates.drupal.org/release-history/drupal/11.x → Error
https://updates.drupal.org/release-history/drupal/all → Works
Impact
This causes the following issues on Drupal sites:
Warning: Undefined array key "project_status" in
Drupal\package_manager\ProjectInfo->getInstallableReleases()
(line 96 of core/modules/package_manager/src/ProjectInfo.php)Environment
Workaround
Currently, the only workaround is to:
Related Issues
#3470230: No available releases found
#3470260: No release history was found for the requested project (Drupal) - marked as fixed in August 2024
Active
Updates System
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activities found.