DeprecateWatch

Weakforced — support and end-of-life dates

Weakforced 3.2 is the current release, released 2026-08-20, with no end-of-life date published upstream.

Direct answer

Weakforced 3.2 has no published end-of-life date. Data as of 2026-11-18.

All tracked cycles

CycleReleasedActive support endsEnd of life (EOL)LatestStatus
3.22026-08-20—not announced3.2.0No EOL date
3.02025-08-20—2026-08-20
90 days ago
3.0.1End of life
2.122024-08-23—2025-08-20
455 days ago
2.12.1End of life
2.102023-12-05—2025-11-05
378 days ago
2.10.3End of life
2.82022-12-05—2023-12-20
1064 days ago
2.8.0End of life
2.62021-11-24—2022-12-05
1444 days ago
2.6.2End of life
2.42020-08-05—2021-11-24
1820 days ago
2.4.1End of life
2.22019-11-07—2020-08-05
2296 days ago
2.2.2End of life
2.02018-12-11—2019-11-25
2550 days ago
2.0.1End of life

Upgrade path stated in the data

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 Weakforced 3.2 end of life?

No. Weakforced 3.2 has no published end-of-life date in the source data.

How many Weakforced versions are already end of life?

8 of the 9 cycles tracked here have passed their EOL date as of 2026-11-18.

Other Server applications with upcoming deadlines

Source for the cycle table: endoflife.date/weakforced read through the endoflife.date API on 2026-11-18. Machine-readable copy: /api/eol.json (product key weakforced).