← ← Back to all products
Forgejo
Active
Tools & Monitoring Latest Version: 14.0.2 Latest Release: Jan 28, 2026
Forgejo is a self-hosted, community-driven Git forge for code hosting, review, and CI/CD.
Versions
8
Latest Version
14.0.2
Active Support
2
EOL
6
Lifecycle Timeline
Today ↓
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
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 14.0 | Jan 15, 2026 | - | Apr 16, 2026 | 14.0.2 | No | Active |
| 13.0 | Oct 16, 2025 | - | Jan 15, 2026 | 13.0.5 | No | EOL |
| 12.0 | Jul 17, 2025 | - | Oct 16, 2025 | 12.0.4 | No | EOL |
| 11.0 | Apr 16, 2025 | - | Jul 16, 2026 | 11.0.10 | Yes | Active |
| 10.0 | Jan 16, 2025 | - | Apr 16, 2025 | 10.0.3 | No | EOL |
| 9.0 | Oct 16, 2024 | - | Jan 16, 2025 | 9.0.3 | No | EOL |
| 8.0 | Jul 30, 2024 | - | Oct 16, 2024 | 8.0.3 | No | EOL |
| 7.0 | Apr 23, 2024 | - | Jul 17, 2025 | 7.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: 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 13.0?
Forgejo 13.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 14.0.2, released in the 14.0 release cycle.
How many versions of Forgejo are currently supported?
Forgejo currently has 2 actively supported version(s): 14.0, 11.0.
When does Forgejo 14.0 reach end of life?
Forgejo 14.0 is scheduled to reach end of life on Apr 16, 2026.
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.