Forgejo End of Life Dates
other
Developers rely on software that streamlines their workflow, and Forgejo has been a valuable tool since its creation, providing a comprehensive platform for hosting a forge using the Git version control system. This package enables teams to collaborate effectively, utilizing features such as bug tracking, code review, and continuous integration, which are essential for efficient software development. Maintained by a community-driven effort, Forgejo has gained popularity among developers due to its flexibility and customization options. With a strong focus on collaborative development, Forgejo has become an indispensable tool for many development teams.
The end-of-life landscape for Forgejo is a critical aspect that developers need to be aware of, with a total of 9 versions released so far, out of which 7 have already reached their end-of-life. Currently, only 2 versions remain active, with the latest stable version being 11.0.15. Notably, version 11.0 is scheduled to expire on 2026-07-16, marking an important milestone for developers who are still using this version. It is also worth mentioning that version 14.0 reached its end-of-life on 2026-04-30, highlighting the need for developers to stay up-to-date with the latest versions to ensure continued support and security.
Given the current security landscape, Forgejo has a remarkably clean record, with a total of 0 CVEs tracked, and consequently, 0 critical CVEs. As a result, there is no most affected version, and the KEV status is not applicable in this case. This exemplary security record is a testament to the dedication of the maintenance team. However, developers should still remain vigilant and take proactive action to ensure the security of their projects by regularly updating to the latest stable versions and monitoring the official Forgejo channels for any security-related announcements or updates.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 16.0 | Jul 16, 2026 | — | Oct 29, 2026 | in 97d | 16.0.1 | — | Active | |
| 15.0 LTS | Apr 16, 2026 | — | Jul 15, 2027 | in 356d | 15.0.5 | — | Active | |
| 14.0 | Jan 15, 2026 | — | Apr 30, 2026 | 85d ago | 14.0.5 | — | EOL | |
| 13.0 | Oct 16, 2025 | — | Jan 29, 2026 | 176d ago | 13.0.5 | — | EOL | |
| 12.0 | Jul 17, 2025 | — | Oct 16, 2025 | 281d ago | 12.0.4 | — | EOL | |
| 11.0 LTS | Apr 16, 2025 | — | Jul 16, 2026 | 8d ago | 11.0.16 | — | EOL | |
| 10.0 | Jan 16, 2025 | — | Apr 16, 2025 | 464d ago | 10.0.3 | — | EOL | |
| 9.0 | Oct 16, 2024 | — | Jan 16, 2025 | 554d ago | 9.0.3 | — | EOL | |
| 8.0 | Jul 30, 2024 | — | Oct 16, 2024 | 646d ago | 8.0.3 | — | EOL | |
| 7.0 LTS | Apr 23, 2024 | — | Jul 17, 2025 | 372d ago | 7.0.16 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
