Forgejo pushes v15 release candidates and draws a hard line on AI in March report

April 12, 2026
aisecurityprivacylaw
A broken laptop screen displayed with colorful glitch being held by a person.
Photo by Beyzanur K. on Pexels

Releases

Forgejo has cut the v15.0.0 branch and scheduled the release for April 16, and it has been reported that code.forgejo.org is already running the release candidate to catch bugs early. Testers are being asked to try v15 on the v15.next.forgejo.org preview, on staging, or even on live instances if they’re brave — binaries and OCI images are available, and maintainers are reminded to read the release notes and back up before upgrading. Meanwhile, the Runner saw two point releases (v12.7.2 and v12.7.3), the latter adding a runner-specific user agent and a handful of bug and dependency fixes.

Security work shipped in March as well: v11.0.11 and v14.0.3 were released on March 9 (the v14 chart also bumped to helm v16.2.1), delivering seven fixes in total; an additional security patch followed on April 10. Forgejo continues to publish advance warnings for security releases — not the details, but enough to let admins plan — and encourages reporting regressions and security issues through the issue tracker or the security policy channels.

Governance and community work

Big governance news: it has been reported that the community reached consensus to prohibit AI-generated contributions after confusion over compatibility with Forgejo’s licensing. That’s the emotional center of this month’s report — a community drawing a clear line in the sand about tooling and trust. All contributors are required to comply with the revised AI agreement; expect conversations about enforcement and edge cases to continue in the chatrooms.

On the feature front, v15 will bring repo-specific access tokens (better-granular permissions vs. deploy keys), work continues on migrating legacy INI strings to JSON-based localization components, and a discussion remains open about caching remote OCI packages — the team wants user feedback to avoid building a solution that fits nobody. Want to help? Test the RC, file issues, join the discussion. It’s your instance after all — who wouldn’t want to pitch in?

Sources: forgejo.org, Lobsters