apache groovy end of life dates — full support timeline
2 of 5 tracked apache groovy 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 |
|---|---|---|---|---|
| 5.0 | 2025-08-21 | not announced | 5.0.8 | supported |
| 4.0 | 2022-01-25 | not announced | 4.0.33 | supported |
| 3.0 | 2020-02-10 | not announced | 3.0.25 | supported |
| 2.5 | 2018-05-30 | 2026-04-30 | 2.5.23 | ended |
| 2.4 | 2015-01-21 | ended | 2.4.21 | ended |
Who is affected
Anyone running an unsupported apache groovy 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/apache-groovy, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next apache groovy deadline
You are reading this because a apache groovy 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 apache groovy and related deadline as it is announced, with exact dates and primary sources.
Watch apache groovy deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.