Forgejo v13.0 is available. A new moderation tool is available to report inappropriate user behavior or content that should be looked at by instance administrators. Two factor authentication (TOTP, etc.) can be enforced on the entire instance for all users or instance administrators. Forgejo Actions usability was improved with static checking of workflow files and access to the logs of all run attempts.
Read more →The Forgejo v13.0 branch has been cut and the release is scheduled for October 16. Please consider testing it out and sharing your feedback to help us improve it. Forgejo Runner v11 has been released and is now licensed under GPLv3+. Improvements were made to the documentation regarding the Runner setup. Work on improving and securing database interaction has begun. There is an ongoing strong enthusiasm for translating Forgejo.
Read more →A Forgejo security release was published, fixing nine low severity vulnerabilities. The Forgejo contributors agreed on rules for the use of AI and the documentation is nearly complete. The runner is considered secure enough to be used in production.
Read more →The Forgejo v12 release was on time. The runner saw significant progress and the release tooling was improved. Discussions emerged regarding AI contributions, contributor attributions in the documentation, and the future of communication. An NLnet grant ended, allowing time for a retrospective.
Read more →Forgejo v12.0 is available. The User eXperience (UX) and User Interface were improved for the user profile page, the review of pull requests one commit at a time and Forgejo Actions notifications when a job fails. Pull request conflict checking was made faster and more resource efficient. SSH can be used instead of OpenPGP for instance signing. A default robots.txt is included by default to help mitigate excessive crawling. It also comes with a number of other UX, performance and security improvements.
Read more →