JReleaser — support and end-of-life dates
JReleaser 1 is the current release, released 2022-04-10, with no end-of-life date published upstream.
- 1 of its 2 tracked cycles have passed their EOL date (earliest tracked cycle 0)
Direct answer
JReleaser 1 has no published end-of-life date. Data as of 2026-11-18.
All tracked cycles
| Cycle | Released | Active support ends | End of life (EOL) | Latest | Status |
|---|---|---|---|---|---|
| 1 | 2022-04-10 | — | not announced | 1.27.0 | No EOL date |
| 0 | 2021-04-10 | 2022-04-10 | 2022-04-10 1683 days ago | 0.10.0 | End of life |
Upgrade path stated in the data
- No successor is stated in the upstream data for this product.
This is not a recommendation from DeprecateWatch. It repeats what the upstream source states, plus the newest cycle that is still inside its published support window.
Questions this page answers
Is JReleaser 1 end of life?
No. JReleaser 1 has no published end-of-life date in the source data.
How many JReleaser versions are already end of life?
1 of the 2 cycles tracked here have passed their EOL date as of 2026-11-18.
Other Desktop & mobile apps with upcoming deadlines
- Palo Alto Networks Cortex XDR agent — next EOL 2026-11-22 (9.1)
- Firefox — next EOL 2026-11-24 (160)
- LibreOffice — next EOL 2026-11-30 (26.2)
- Docker Engine — next EOL 2026-12-04 (25.0)
- dbt Core — next EOL 2026-12-19 (1.11)
- NVIDIA Driver — next EOL 2026-12-22 (r590-windows)
- Bazel — next EOL 2026-12-31 (7)
- Composer — next EOL 2026-12-31 (2.2)
Source for the cycle table: endoflife.date/jreleaser
read through the endoflife.date API on 2026-11-18. Machine-readable copy:
/api/eol.json (product key jreleaser).