Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The logic is already in place for https://www.drupal.org/8/download to redirect to 9.0.0 once it is released, making the 8 in the path not quite right. It should be replaced with something like
- …/latest-core-release
- …/latest-drupal-release
- …/current/download
Proposed resolution
- Create a new redirect https://www.drupal.org/latest-release with the same target as the current one: it will go to the latest stable release of the current major version of Drupal.
- Replace links to https://www.drupal.org/8/download on d.o with the new link.
Comments
Comment #3
drummbenjifisher raised this issue in Slack.
Comment #4
benjifisherThe status is NR, but I am not sure how to test this.
The existing redirect (/8/download) is used on https://www.drupal.org/download (with the link text "read release notes"). Maybe the IS should mention that we should update that once the new redirect is created.
Comment #5
drummWe need to review & pick one of the 3 options, or something else.
The implementation is straightforward and can be deployed within 15 minutes, including redirecting
8/downloadto the new path and updating https://www.drupal.org/download.Comment #6
berdirNot sure if I understand the goal here.
For this to be useful for the critical core issue #3098475: Add more strict checking of hook_update_last_removed() and better explanation we _need_ it to point to the latest D8 release, because we want to point people to the best release they should update to before updating to D9. Sounds to me like the goal is now to change the URL to make it consistent with the current implementation and not the other way round :)
Could we make it download/ or something like that, so we can do download/8, download/9, ...?
Comment #7
drummAh, I didn’t undertand the scope of the original request.
Currently,
/8/downloadis misleading, not restricted to Drupal 8.*, and we should fix that. That’s this issue.And there should be something to link to for “the latest/last Drupal 8.* release.” Currently, there is https://www.drupal.org/project/drupal/releases?api_version%5B%5D=7234, but that will be changing in the next few weeks, too. “API version” does not make sense when projects are all using semantic versioning, and are compatible with arbitrary ranges of Drupal core versions.
Comment #10
drummThe canonical path for this is now https://www.drupal.org/latest-release
Comment #11
benjifisherI am updating the IS with a more detailed description of what (I think) has already been done. @drumm, can you confirm that my description is accurate?
I believe that we all have the same thing in mind, but #6 shows that there is still some uncertainty.
Comment #12
drummThis is just making the link more accurate. It goes to the latest version of Drupal, 8, 9, or whatever. Wherever we can, we’re removing the concept of Drupal 8/9/etc, since the major version doesn’t matter as much.
If we do need some sort of redirect to the last 8 version, that’ll be a separate issue. If it can work, I recommend linking to https://www.drupal.org/project/drupal/releases?api_version%5B%5D=7234 for now, and watching #3104886: Update/remove API version filter on “All releases” pages.
Comment #13
benjifisherIn that case, I will update the IS again, and we will use a different link in #3098475: Add more strict checking of hook_update_last_removed() and better explanation.