jhipster end of life dates — full support timeline
9 of 10 tracked jhipster 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 |
|---|---|---|---|---|
| 9 | 2026-03-11 | not announced | 9.2.0 | supported |
| 8 | 2023-11-02 | 2026-03-11 | 8.11.0 | ended |
| 7 | 2021-03-21 | 2023-11-02 | 7.9.4 | ended |
| 6 | 2019-05-02 | 2021-03-21 | 6.10.5 | ended |
| 5 | 2018-06-20 | 2019-05-02 | 5.8.2 | ended |
| 4 | 2017-02-02 | 2018-06-20 | 4.14.5 | ended |
| 3 | 2016-03-23 | 2017-02-02 | 3.12.2 | ended |
| 2 | 2015-01-12 | 2016-03-23 | 2.27.2 | ended |
| 1 | 2014-09-01 | 2015-01-09 | 1.10.2 | ended |
| 0 | 2013-10-21 | 2014-09-01 | 0.18.1 | ended |
Who is affected
Anyone running an unsupported jhipster 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/jhipster, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next jhipster deadline
You are reading this because a jhipster 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 jhipster and related deadline as it is announced, with exact dates and primary sources.
Watch jhipster deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.