EOL.Wiki EOL.Wiki
← ← Back to all products

Forgejo

Active
Tools & Monitoring Latest Version: 15.0.3 Latest Release: Jun 10, 2026

Forgejo is a self-hosted, community-driven Git forge for code hosting, review, and CI/CD.

Versions

9

Latest Version

15.0.3

Active Support

2

EOL

7

Lifecycle Timeline

Today
15.0
15.0
14.0
14.0
13.0
13.0
12.0
12.0
11.0
11.0
10.0
10.0
9.0
9.0
8.0
8.0
7.0
7.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
15.0Apr 16, 2026YesJul 15, 202715.0.3
Yes
Active
14.0Jan 15, 2026NoApr 30, 202614.0.5No
EOL
13.0Oct 16, 2025NoJan 29, 202613.0.5No
EOL
12.0Jul 17, 2025NoOct 16, 202512.0.4No
EOL
11.0Apr 16, 2025YesJul 16, 202611.0.15
Yes
Active
10.0Jan 16, 2025NoApr 16, 202510.0.3No
EOL
9.0Oct 16, 2024NoJan 16, 20259.0.3No
EOL
8.0Jul 30, 2024NoOct 16, 20248.0.3No
EOL
7.0Apr 23, 2024NoJul 17, 20257.0.16
Yes
EOL

Frequently Asked Questions

Which versions of Forgejo have reached end of life?
The following Forgejo versions have reached end of life and no longer receive security updates: 14.0, 13.0, 12.0, 10.0, 9.0, 8.0, 7.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Forgejo 14.0?
Forgejo 14.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Forgejo?
The latest version of Forgejo is 15.0.3, released in the 15.0 release cycle.
How many versions of Forgejo are currently supported?
Forgejo currently has 2 actively supported version(s): 15.0, 11.0.
When does Forgejo 15.0 reach end of life?
Forgejo 15.0 is scheduled to reach end of life on Jul 15, 2027.
What should I do when Forgejo reaches end of life?
When a Forgejo version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.