jruby end of life dates — full support timeline
4 of 7 tracked jruby 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 |
|---|---|---|---|---|
| 10.1 | 2026-04-21 | not announced | 10.1.1.0 | supported |
| 10.0 LTS | 2025-04-14 | 2028-04-01 | 10.0.6.0 | supported |
| 9.4 | 2022-11-23 | not announced | 9.4.15.0 | supported |
| 9.3 | 2021-09-22 | 2024-06-26 | 9.3.15.0 | ended |
| 9.2 | 2018-05-24 | 2022-06-27 | 9.2.21.0 | ended |
| 9.1 | 2016-05-02 | 2018-04-20 | 9.1.17.0 | ended |
| 9.0 | 2015-07-21 | 2016-01-30 | 9.0.5.0 | ended |
Who is affected
Anyone running an unsupported jruby 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/jruby, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next jruby deadline
You are reading this because a jruby 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 jruby and related deadline as it is announced, with exact dates and primary sources.
Watch jruby deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.