grunt end of life dates — full support timeline
6 of 7 tracked grunt 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 |
|---|---|---|---|---|
| 1.6 | 2023-01-28 | not announced | 1.6.3 | supported |
| 1.5 | 2022-04-10 | 2023-01-28 | 1.5.3 | ended |
| 1.4 | 2021-04-22 | 2022-04-10 | 1.4.1 | ended |
| 1.3 | 2020-08-18 | 2021-04-22 | 1.3.0 | ended |
| 1.2 | 2020-07-03 | 2020-08-18 | 1.2.1 | ended |
| 1.1 | 2020-03-16 | 2020-07-03 | 1.1.0 | ended |
| 1.0 | 2016-04-04 | 2020-03-16 | 1.0.4 | ended |
Who is affected
Anyone running an unsupported grunt 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/grunt, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next grunt deadline
You are reading this because a grunt 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 grunt and related deadline as it is announced, with exact dates and primary sources.
Watch grunt deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.