Forgejo
forgejo@floss.social
<p>Beyond coding. We forge.</p>
Posts
-
Post #4301283
#Forgejo 15.0.5 was just released! We recommend that all installations are upgraded to the latest version. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #4253750
#Forgejo 16.0.2 and 15.0.6 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #3981727
#Forgejo 16.0.1 was just released! We recommend that all installations are upgraded to the latest version. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #3855096
#Forgejo 16.0.0 was just released! We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #3694185
#Forgejo 15.0.4 and 11.0.16 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #3649834
A security vulnerability labelled CVE-2026-27771 affecting Forgejo and Gitea is being widely reported recently. Packages in Forgejo are visible to unauthenticated users if they are published under a public owner, as designed. It is not a security vulnerability, but a misunderstanding about the permissions and a good opportunity for users to review that they are not in a misconfigured state. Please see the statement issued by the security team here for more details: https://codeberg.org/forgejo...
-
Post #3649833
The #Forgejo monthly report was published ✨ Forgejo v15 was released, along with security releases. The Forgejo Security Team responds to community concerns. The Forgejo Runner had multiple releases, the Forgejo Helm chart v17 was released and the Forgejo v16 release is progressing. https://forgejo.org/2026-05-monthly-report
-
Post #3248897
#Forgejo 15.0.3 and 11.0.15 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #2486924
Did you know: #Forgejo always announces security updates in advance (usually at least one week beforehand) to give you time to prepare and be ready when the release is published. Announcements are made via this tracker: https://codeberg.org/forgejo/security-announcements/issues. You can &quot;watch&quot; the repo or subscribe to the RSS feed to stay informed.
-
Post #2442811
#Forgejo 15.0.2 and 11.0.14 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #1811506
The author of the recent 'Carrot disclosure' blog post has contacted the Forgejo Security team with their findings. The issues raised concern defence-in-depth improvements and denial-of-service risks. There is no known RCE exploit possible without internal server credentials. 1/2
-
Post #1774600
#Forgejo 15.0.1, 14.0.5 and 11.0.13 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #1193884
#Forgejo 15.0.0 was just released! Access tokens can now be restricted to specific repos. New containers are now auto-linked if possible. Responsiveness and accessibility of the UI were improved. Forgejo actions gained multiple new features. As an LTS version, it will be supported until 15 July 2027. Check out the blog post at https://forgejo.org/2026-04-release-v15-0/ #forgejorelease
-
Post #1160987
The next major Forgejo release and LTS version (v15) is about to be released tomorrow, April 16. Additionally, the Forgejo community invites all users to a release and upgrade party starting 16.00 UTC (18 CEST). It can be used to review the release cycle, exchange feedback and discuss future plans. Also, Admins are invited to perform upgrades of their instances during the meeting and get help from maintainers in case of any issues. Audio + chat meeting on BigBlueButton: https://lecture.senfcal...
-
Post #1098642
#Forgejo 14.0.4 and 11.0.12 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #1098641
The #Forgejo monthly report was published ✨ The Forgejo v15.0 branch has been cut and the release is scheduled for April 16. Security releases for Forgejo were published. The AI-Agreement was updated. code.forgejo.org is not a free public git hosting. https://forgejo.org/2026-03-monthly-report
-
Post #960333
The Forgejo v15 branch has been cut and the release is scheduled for April 16. You can help us by testing it in advance of the release. You can try it out on a test instance, or upgrade to a pre-release build early (please, keep a backup). It can be tried on https://v15.next.forgejo.org/, and pre-release binaries (https://codeberg.org/forgejo-experimental/forgejo/releases/tag/v15.0-test) and OCI images (https://codeberg.org/forgejo-experimental/-/packages/container/forgejo/versions?q=15.0) are...
-
Post #811077
The #Forgejo monthly report was published ✨ Forgejo was present at FOSDEM. The Forgejo runner received multiple bug fixes and new features. The helm chart received two minor changes. Improvements were made to the infrastructure. https://forgejo.org/2026-02-monthly-report
-
Post #749163
#Forgejo 14.0.0 was just released! Issues search now has inline filters. Web file editor was replaced with CodeMirror. CSRF protection is now stateless. Forgejo actions gained new features and better trust management. Foreign keys are now supported to ensure database consistency. Check out the blog post at https://forgejo.org/2026-01-release-v14-0/ #forgejorelease
-
Post #611084
#Forgejo 14.0.3 and 11.0.11 were just released! They are security releases. We recommend that all installations are upgraded to the latest version as soon as possible. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #316641
#Forgejo 14.0.2 was just released! We recommend that all installations are upgraded to the latest version. Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues. #forgejorelease
-
Post #316640
The #Forgejo monthly report was published ✨ Forgejo v14 was released on time. Some regressions were quickly escalated and fixed. A security release was published for v11 and v13. A lot of work has been done around the runner: New features and QA. There are ongoing discussions about improving the issue reporting workflow and the license and copyright attribution in the codebase. Work on federation is progressing. The website was moved to our own infrastructure. https://forgejo.org/2026-01...