Forgejo End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 15.0.12 LTS

Forgejo end of life (EOL) and end of support (EOS) dates: 9 Forgejo versions have reached EOL, including Forgejo 16.0 (EOL date: Oct 29, 2026) — no longer receiving security updates or patches. Forgejo 17.0 reaches its End of Support date on Jan 28, 2027 — plan your upgrade path now. Forgejo 15.0.12 LTS is the current supported release, with support through Jul 15, 2027. Also see Chef Supermarket end of support life for related end-of-life information.

Forgejo end of life dates timeline — release schedule chart of the 8 most recent Forgejo versions, mapping security support windows against their EOL dates
Forgejo end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Forgejo releases of 11 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Forgejo EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Forgejo Releases - Active EOS/EOSL Support (1)

Release Released Security Support Latest LTS
15.0 (LTS) (7 months ago) (in 7 months) 15.0.12 (3 days ago) LTS

Forgejo Releases Nearing End of Life - Support Ending Soon (1)

Important: The following Forgejo releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Released Security Support Latest LTS
17.0 (1 month and 6 days ago) (in 2 months) 17.0.2 (3 days ago) -

Forgejo End of Life (EOL) Releases - No Longer Supported (9)

Release Released Security Support Latest LTS
16.0 (4 months ago) (3 weeks and 2 days ago) 16.0.7 (3 weeks and 5 days ago) -
14.0 (10 months ago) (6 months ago) 14.0.5 (6 months ago) -
13.0 (1 year and 1 month ago) (9 months ago) 13.0.5 (10 months ago) -
12.0 (1 year and 4 months ago) (1 year and 1 month ago) 12.0.4 (1 year and 2 months ago) -
11.0 (LTS) (1 year and 7 months ago) (4 months ago) 11.0.16 (4 months ago) LTS
10.0 (1 year and 10 months ago) (1 year and 7 months ago) 10.0.3 (1 year and 7 months ago) -
9.0 (2 years and 1 month ago) (1 year and 10 months ago) 9.0.3 (1 year and 11 months ago) -
8.0 (2 years and 3 months ago) (2 years and 1 month ago) 8.0.3 (2 years and 2 months ago) -
7.0 (LTS) (2 years and 6 months ago) (1 year and 4 months ago) 7.0.16 (1 year and 4 months ago) LTS

Running a self-hosted software forge means you choose when to update, so knowing the Forgejo end of life dates keeps you from running code that no longer gets fixes. As of 27 October 2026, v16.0 has just two days of support left, which makes 17.0 and the LTS 15.0 line the versions to plan around.

Forgejo End of Life Dates for Every Version

The table below shows when each release stops receiving fixes, based on the dates in the project's published schedule. Days supported counts from the release date to the last day of support.

VersionRelease dateSupport endsDays supported
15.0 (LTS)16 April 202615 July 2027455
16.016 July 202629 October 2026105
17.015 October 202628 January 2027105
18.014 January 202729 April 2027105
19.0 (LTS)15 April 202713 July 2028455

Release Numbers You Can Still Run

Only the release numbers 15.0, 16.0 and 17.0 are a supported release today. Older lines, such as 14.0, which ended on 30 April 2026, and the 11.0 LTS, which ended on 16 July 2026, get no further fixes.

Forgejo v16.0 Is Supported Until 29 October

If you run Forgejo v16.0, it is supported until 29 October 2026. Move to Forgejo v17.0, released on 15 October, or to the LTS line. Server administrators handling hosting for a team should schedule this maintenance now.

Forgejo Release Schedule and Long Term Support

The release schedule is time based, which gives the community predictable dates. Because Forgejo is free software and fully open source, the dates are public and you can plan years ahead. Support is the part that matters most for stability.

Stable Releases Every Quarter

Stable releases arrive every quarter, and each of the major releases receives fixes for three months. That is why 16.0, 17.0 and 18.0 each show 105 days of support.

Why Each LTS Release Lasts Longer

The LTS line appears once a year in the spring, and an LTS release gets critical bugfixes for one year and three months, or 455 days. Teams that prefer long term support over frequent change should choose it. Any non-LTS release is the opposite trade: newer features, shorter life, so a stable-minded team lands on long-term support releases only about once a year.

Security Releases and Advance Notice

Fixes ship as security releases with advance notice on the security-announcements issue tracker. Follow it so you can reserve time for patching.

What Happens When a Forgejo Version Is No Longer Supported

Once a Forgejo version passes its end of life, the fixes stop, and every later vulnerability stays open on your server. Compatibility with new tooling and migrated repositories also drifts over time.

Security Support and Patch Releases Stop Together

Without security support, the security team will not backport fixes to your line. Both patch releases and the next patch release on that line stop, so a git host that stores your Git history, your Git LFS files and your authentication data stays exposed to every newly found flaw.

Breaking Changes in Recent Major Releases

Moving off a line before its support ends means reading the breaking changes first. Version 16.0 requires administrators to set a trusted proxy list for a reverse proxy in app.ini, and 17.0 starts the deprecation of action run events for any webhook receiver. These events belong to Forgejo Actions, so test your Forgejo Actions workflows and the Forgejo Runner setup after the jump. A license fix also removed EXIF stripping, and migration of a mirror that points at a renamed repository now fails until you update its URL. Each mirrored repository and every repository hook that touches Git deserves a check, and smaller avatars now save bandwidth.

Upgrading Before the Release Date Passes

Upgrading is a quick swap, yet it deserves care. This keeps you stay up to date within a supported line, and the release notes plus the documentation explain every step.

Take a Full Backup First

Make a full backup before touching anything, since a rollback needs the old data and the old files.

Upgrade Guide for Container Images and Binary

Follow the upgrade guide. Replace the binary, or pull new container images, including OCI images in a rootless variant, under docker or Podman. A tag such as 17.0 follows each patch automatically.

Try a Test Instance with Daily Releases

The project runs a test instance built from daily releases of the development branch, so you can preview a fix before it ships.

Following the Forgejo Long-Term Support Calendar

Subscribe to the RSS feed or the iCalendar feed on endoflife.date to be reminded before Forgejo end of life for your version, such as 29 October 2026 for v16.0 or 15 July 2027 for the LTS 15.0 line. The feeds follow the same dates as the table above.

EOL dates of related software products