Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
9.5.x now shows a warning in the status report
Covered until 2023-Nov. / Update to a supported minor version soon to continue receiving security updates.
This is controlled by a constant in \Drupal\update\ProjectSecurityData:
const SECURITY_COVERAGE_ENDING_WARN_DATE_9_5 = '2023-05-14';
Users have reported that the warning is poorly worded. This is for two reasons:
- There are no more supported minor versions for Drupal 9.5; it should probably tell the user they need to update to Drupal 10.
- 9.4.x is still supported for another month, so the warning feels like it's a bit early.
Steps to reproduce
Install 9.5.x and update.module.
Proposed resolution
Discussed with the release managers. @catch said:
Should it say 'Update to Drupal 10 soon to continue receiving security updates' and maybe push it back until the day of 10.1.0's release?
@xjm said:
I think maybe it's a typo and it was supposed to be 2023-06-14 but not sure.
Not that changing it now will not have much impact -- at most it will help from the June bugfix release to the 10.1 release date. I guess at least removing the word "minor" would help until D9's EOL.
Remaining tasks
Remove 'minor' from the message.
User interface changes
Removed 'minor' from this message
API changes
None.
Data model changes
None.
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Screenshot 2024-05-31 at 18-11-20 Status report Drupal.png | 26.55 KB | quietone |
Issue fork drupal-3361728
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
xjmAdding missing keyword "not" from my slack tell. 😂
Comment #3
xjmConverting this to an issue for fixing similar messages for Drupal 10 (once we add them), and marking postponed, since it's definitely not fixable in D9 anymore.
Comment #4
quietone commentedComment #5
quietone commentedChanging the status was a mistake.
Comment #6
quietone commentedI agree with #3 that the warning date for 9.5 is likely a typo.
The message is created in getDateEndRequirement which does not have information about the next major. That is why I implemented the suggestion to remove 'minor'. It is by the simplest action to take to improve the message.
Comment #7
quietone commentedComment #8
smustgrave commented@quietone did you mean to push a change?
Comment #10
quietone commentedYes, I did. This time I have made an MR.
Comment #11
smustgrave commentedCool, have done that before too.
Change seems straight forward enough
Comment #12
longwaveCan we also change the date format to something more human readable while we are here?
Covered until 2023-Nov.Suggested change:
Covered until November 2023.Comment #13
xjmThe existing date formats were chosen for being reasonably understandable internationally, rather than having to get the date formatter involved for a status report message.
If we want to propose changing that too, I would suggest a separate issue.
Comment #14
ankitv18 commentedRTBC+1 on the basis of @xjm comment#13
Comment #17
longwaveCommitted to 11.x and 10.4.x as this is a translatable string change.
Committed and pushed d49ffa40d1 to 11.x and bd6f329075 to 10.4.x. Thanks!
Comment #19
longwave...and backported to 11.0.x given this is tagged under the meta for 11.0.0-beta2.
Comment #21
xjmAmending attribution.