forgejo end of life dates — full support timeline
8 of 10 tracked forgejo 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 |
|---|---|---|---|---|
| 16.0 | 2026-07-16 | 2026-10-29 | 16.0.2 | ends soon |
| 15.0 LTS | 2026-04-16 | 2027-07-15 | 15.0.6 | supported |
| 14.0 | 2026-01-15 | 2026-04-30 | 14.0.5 | ended |
| 13.0 | 2025-10-16 | 2026-01-29 | 13.0.5 | ended |
| 12.0 | 2025-07-17 | 2025-10-16 | 12.0.4 | ended |
| 11.0 LTS | 2025-04-16 | 2026-07-16 | 11.0.16 | ended |
| 10.0 | 2025-01-16 | 2025-04-16 | 10.0.3 | ended |
| 9.0 | 2024-10-16 | 2025-01-16 | 9.0.3 | ended |
| 8.0 | 2024-07-30 | 2024-10-16 | 8.0.3 | ended |
| 7.0 LTS | 2024-04-23 | 2025-07-17 | 7.0.16 | ended |
Who is affected
Anyone running an unsupported forgejo 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/forgejo, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next forgejo deadline
You are reading this because a forgejo 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 forgejo and related deadline as it is announced, with exact dates and primary sources.
Watch forgejo deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.