drush end of life dates — full support timeline
7 of 9 tracked drush releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 13 | 2024-08-02 | not announced | 13.7.6 | supported |
| 12 | 2023-06-03 | not announced | 12.5.3 | supported |
| 11 | 2022-01-11 | 2023-11-30 | 11.6.0 | ended |
| 10 | 2019-10-31 | 2022-01-31 | 10.6.2 | ended |
| 9 | 2018-01-24 | 2020-05-31 | 9.7.3 | ended |
| 8 | 2015-11-19 | 2025-01-31 | 8.5.0 | ended |
| 7 | 2015-05-20 | 2017-07-31 | 7.4.2 | ended |
| 6 | 2013-08-16 | 2015-12-31 | 6.7.0 | ended |
| 5 | 2012-03-23 | 2015-05-31 | 5.11.0 | ended |
Who is affected
Anyone running an unsupported drush release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/drush, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next drush deadline
You are reading this because a drush release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every drush and related deadline as it is announced, with exact dates and primary sources.
Watch drush deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.