Forgejo v15.0 Released: Milestone 100th Version With Enhanced Security and UI Improvements
Key Takeaways
- ▸Forgejo v15.0 marks the 100th release of the community-developed code collaboration platform
- ▸Repository-specific access tokens enable more granular and secure API access control
- ▸Enhanced Forgejo Actions support includes reusable workflow expansion and OpenID Connect integration
Summary
Forgejo, the lightweight, community-developed self-hosted code collaboration platform, has released version 15.0 on April 16, 2026, marking its 100th release milestone. The release focuses on refining day-to-day usability and security while introducing new capabilities for advanced Forgejo Actions usage. Key improvements include UI enhancements for issue filtering and release lists, repository-specific access tokens for more secure API interactions, and auto-linking of containers to repositories.
The update brings significant security enhancements and workflow improvements, including support for expanding reusable workflows in Forgejo Actions, OpenID Connect support for secure third-party system access, and improved Forgejo Runner registration with ephemeral runner capabilities for autoscaling. However, the release includes breaking changes that administrators should be aware of, including modified default cookie names that will require users to re-login, Docker rootless configuration file location changes, and authorization changes to repository APIs.
- Breaking changes require careful upgrade planning, including cookie name modifications and Docker configuration updates
- Auto-linking containers to repositories simplifies repository management workflows
Editorial Opinion
Forgejo v15.0 demonstrates mature platform evolution with a strong focus on security and developer experience. The introduction of repository-specific access tokens is particularly valuable for organizations managing multiple projects, addressing a critical security gap in token management. While the breaking changes are disruptive, they represent necessary modernization—stripped branding from default cookies and updated Docker configurations align the platform with contemporary containerization standards.



