weakforced end of life dates — full support timeline
7 of 8 tracked weakforced 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 |
|---|---|---|---|---|
| 3.0 | 2025-08-20 | not announced | 3.0.1 | supported |
| 2.12 | 2024-08-23 | 2025-08-20 | 2.12.1 | ended |
| 2.10 | 2023-12-05 | 2024-08-23 | 2.10.3 | ended |
| 2.8 | 2022-12-05 | 2023-12-20 | 2.8.0 | ended |
| 2.6 | 2021-11-24 | 2022-12-05 | 2.6.2 | ended |
| 2.4 | 2020-08-05 | 2021-11-24 | 2.4.1 | ended |
| 2.2 | 2019-11-07 | 2020-08-05 | 2.2.2 | ended |
| 2.0 | 2018-12-11 | 2019-11-25 | 2.0.1 | ended |
Who is affected
Anyone running an unsupported weakforced 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/weakforced, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next weakforced deadline
You are reading this because a weakforced 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 weakforced and related deadline as it is announced, with exact dates and primary sources.
Watch weakforced deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.