Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.The update status XML system is starting to show its age. We can improve:
- Use more robust file hashes with #1441870: Provide SHA-256 or better hashes for download files
- Save a bit of bandwidth by moving from XML to JSON.
- Better support more edge cases, like a branch of a project becoming unsupported.
- More-descriptive support and security information.
Comments
Comment #2
drummComment #3
drummComment #4
Wim LeersCan't we add better edge case support and better support & sec information to the existing format? We'll have to continue to support XML update status information for another decade anyway probably.
Comment #5
drummYes, the existing system will be in place indefinitely. It may end up being okay to keep extending.
Comment #7
drummRyan had an idea in a meeting this came up in a meeting.
Right now we have API-compatibility-specific histories like
And
allfor everything:We could add
currentwhich:Comment #8
drummSince #3085041: Drupal core 9.x.x releases should not attach API compatibility term, Drupal 9.0.x is not at https://updates.drupal.org/release-history/drupal/9.x. That just has some junk about the former “9.x” release which I’ll remove, see #2864048: Delete the 9.x branch and its associated release.
Also with 8.x-… modules optionally being compatible with Drupal 9, grouping modern/current releases by
8.xor9.xdoesn’t make sense.Comment #9
Wim LeersIs #8 saying that the logical/semantical changes that D9 is forcing us to deal with, we might as well execute on this issue's original intent and scope?
Comment #10
drummProbably not the whole scope. XML isn’t a “cool” file format, but this really should be backported to D8, #3074993: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates. Completely changing the format would probably kill any chance of that happening.
(I could see putting semver contrib releases in the 8.x XML if their .info file says they are compatible with D8. That would probably confuse some logic in update.module on sites that haven’t updated.)
Comment #11
drummComment #18
drummThis should not affect existing update status XML, it adds a new …-current.xml, which is described at #3074993-18: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates