flux end of life dates — full support timeline
8 of 11 tracked flux 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 |
|---|---|---|---|---|
| 2.9 | 2026-06-30 | not announced | 2.9.3 | supported |
| 2.8 | 2026-02-24 | not announced | 2.8.8 | supported |
| 2.7 | 2025-09-30 | not announced | 2.7.5 | supported |
| 2.6 | 2025-05-29 | 2026-06-30 | 2.6.4 | ended |
| 2.5 | 2025-02-20 | 2026-02-24 | 2.5.1 | ended |
| 2.4 | 2024-09-30 | 2025-09-30 | 2.4.0 | ended |
| 2.3 | 2024-05-13 | 2025-05-29 | 2.3.0 | ended |
| 2.2 | 2023-12-12 | 2025-02-20 | 2.2.3 | ended |
| 2.1 | 2023-08-24 | 2024-09-30 | 2.1.2 | ended |
| 2.0 | 2023-07-05 | 2024-05-13 | 2.0.1 | ended |
| 1.25 | 2022-03-30 | 2022-11-02 | 1.25.4 | ended |
Who is affected
Anyone running an unsupported flux 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/flux, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next flux deadline
You are reading this because a flux 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 flux and related deadline as it is announced, with exact dates and primary sources.
Watch flux deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.