#Forgejo 17.0.0 was just released!
Repository funding links are supported. Repositories can be migrated from Bitbucket Data Center. LFS support is revamped. Job summaries from Forgejo Actions jobs are displayed.
Check out the blog post at https://forgejo.org/2026-10-release-v17-0/.
#forgejorelease
10/15/2026, 9 engagements
#Forgejo 16.0.4 and 15.0.8 were just released! They are critical 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
9/10/2026, 1 engagement
#Forgejo 16.0.3 and 15.0.7 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
8/20/2026, 2 engagements
Forgejo Runner, the program executing workflows of continuous integration in #Forgejo, has been released in version 13.0. It comes with breaking changes that may break current workflows for Forgejo Actions users. These changes improve security, predictability, and maintainability. https://forgejo.org/2026-08-runner-release-v13/
#ForgejoRunner #ForgejoActions #CI
8/5/2026, 2 engagements
#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
7/30/2026, 5 engagements
#Forgejo 16.0.0 was just released!
Repository watch now has options. Authorized Integrations allow secret-less access to the API. Review comments can be placed on multiple lines of code. Improved security of pull mirrors.
Check out the blog post at https://forgejo.org/2026-07-release-v16-0/
#forgejorelease
7/16/2026, 4 engagements
#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
7/15/2026, 2 engagements
#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
7/9/2026, 2 engagements
#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
6/10/2026, 6 engagements
The #Forgejo monthly report was published ✨ Forgejo v15 was released, along with security releases. The Forgejo Runner had multiple releases and the Forgejo Helm chart v17 was released. The Forgejo Security Team responds to community concerns. Forgejo Runner received multiple updates and the Forgejo v16 release is progressing.
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/website/issues/839#issuecomment-15980039
5/28/2026, 4 engagements
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 "watch" the repo or subscribe to the RSS feed to stay informed.
#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
5/12/2026, 9 engagements
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
4/30/2026, 2 engagements
#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
4/16/2026, 7 engagements
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.senfcall.de/ott-hqp-axg-yvm
4/15/2026, 3 engagements
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.
#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
4/10/2026, 1 engagement
#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
3/9/2026, 2 engagements
#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
1/29/2026, 3 engagements
#Forgejo 13.0.4 and 11.0.9 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
1/8/2026, 2 engagements
The #Forgejo monthly report for November was just published! ✨ https://forgejo.org/2025-11-monthly-report/ A security release was published for Forgejo v13 and v11 LTS. There is another way to report accessibility issues that lowers the barrier. User research is still seeking your help. A lot of work has been done regarding federation, and the Dutch government has expressed interest in Forgejo.
The #Forgejo monthly report was published ✨
Forgejo is 3 years old and was made possible by over 1,930 people and and many other free projects. Forgejo v13 was released and security vulnerabilities were fixed. Forgejo-contrib incubated new projects.
Dear #Forgejo admins and users,
We are launching another series of user research interviews in the next weeks and invite you to participate. The 45-minutes interviews help us a lot to learn about your usage of Forgejo.
Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to learn more and to schedule an appointment.
10/29/2025, 5 engagements
#Forgejo 13.0.2 and 11.0.7 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
10/26/2025, 3 engagements
Dear #Forgejo admins, Planning to upgrade to Forgejo v13.0 soon? Join our upgrade party and upgrade together, get help from Forgejo contributors, and get to know the community. Today, 21 October at 16:00 UTC (18:00 CEST). See https://codeberg.org/forgejo/discussions/issues/402 for details.
10/21/2025, 3 engagements
#Forgejo 13.0.1 was just released!
We recommend that all installations are upgraded to the latest version. The v13.0.0 release revealed a bug that has been in the codebase for years and caused the corruption of the Forgejo Actions secrets on instances using PostgreSQL.
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
10/17/2025, 4 engagements
⚠️ Wait for Forgejo v13.0.1 to be released, do not migrate to Forgejo v13.0.0 ⚠️
A bug that could remove part of the Forgejo Actions secrets or make some of them unusable during the migration was discovered.
It will be fixed in Forgejo v13.0.1. If you already migrated, please follow the instructions from the updated release notes.
10/17/2025, 7 engagements
#Forgejo 13.0.0 was just released!
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.
Check out the blog post at https://forgejo.org/2025-10-release-v13-0/
#forgejorelease
10/16/2025, 6 engagements
#Forgejo 11.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
6/18/2025, 1 engagement
The #Forgejo monthly update was published ✨
Ongoing issues with the Matrix chat room were addressed by recreating the room. Users are encouraged to join the new room, as the old room is deprecated. Security updates have been released for versions v11 and v7. Progress continues on the moderation feature funded by
. Work on federated user activity continues, including the ability to follow Forgejo users from GoToSocial.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo is now featured on the official Git website. Forgejo v11.0 was released on 16 April following quick fixes for identified regressions. The Helm chart was updated to version 12 for compatibility. Federation work continues on HTTP signatures and following user activity. The infrastructure faced SSH connection failures and excessive crawling.
#Forgejo 11.0.0 was just released!
We recommend that all installations are upgraded to the latest version.
It comes with a number of new features and improvements making user experience more convenient and productive. It features a new UI language, easy access token regeneration, better search options, and makes it possible to download entire folders in one click. As an LTS version, it will be supported until 15 July 2026.
Read more at https://forgejo.org/2025-04-release-v11-0/
#forgejorelease
4/16/2025, 1 engagement
#Forgejo 10.0.3 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
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
FOSDEM impressions were published and feedback is being collected regarding migrations to Forgejo and commercial usages of Forgejo. code.forgejo.org got hit by a DDoS that was successfully mitigated. A new localization component is now in use and work on federation continued.
⚠️ Codeberg is facing a network level DDoS. Until it is back online, it is possible to use https://code.forgejo.org/forgejo/forgejo/releases as an alternate source for releases.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
New releases, improvements to the website and an update to the current state of federation in Forgejo. January was a productive month that ended in preparations to FOSDEM and allowed some team members to meet in real life for the first time.
⚠️ In the past 48h code.forgejo.org was disrupted by what appears to be a DDoS. The service did not go down but it timed out during a few minutes on several occasions, when receiving hundreds of requests per second originating from tens of thousands of different IP addresses. The devops team is working on it.
#Forgejo 10.0.1 and 7.0.13 were just released! They are security releases.
We strongly recommend that all installations are upgraded to the latest version as soon as possible.
Read more in the companion blog post https://forgejo.org/2025-02-release-v10-0-1/
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
#Forgejo v10.0 was just released! Get it at https://forgejo.org/download/. 🚀
TOTP secrets were made more secure. The UI was made more accessible and reworked to improve the UX. Searching users, repositories, releases and issues was improved. Low German (Plattdüütsch) translation was completed. This is the last version to allow a transparent upgrade from Gitea v1.22 or lower.
Read more at https://forgejo.org/2025-01-release-v10-0/
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
All the best for the new year from Forgejo. We are in the preparations for the upcoming v10 release, have improved testing and automation. A a big thanks to everyone who makes Forgejo a success, including upstream projects and libraries Forgejo depends on.
#Forgejo 9.0.3 and 7.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
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
A security audit and internal preparations have lead to unprecedented security releases for Forgejo and the Forgejo Actions runner. The migration to a new k8s cluster has made huge progress and is now powering the Forgejo-specific services in production. Improvements have been made to the performance and stability of Forgejo as well as to the automated testing process.
#Forgejo v8.0.3 and v7.0.9 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.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo changed its license from MIT to a GNU GPL v3+, it is now copyleft, just like Git. A pull request for federated user activity following using ActivityPub saw significant progress. Space usage quotas for users and organizations was implemented. The Forgejo security policy was published.
Dear Forgejo #admins,
In case you missed it in the release notes, we invite you to our #UpgradeParty to upgrade, set up (and fix in worst-case) our instances together with other #Forgejo admins and contributors.
Join us this Friday at 18.00 CEST / 16.00 UTC. Find all details in the Codeberg Event Calendar: https://codeberg.codeberg.page/Events/events/2024/08-02-forgejo-upgrade-party/
#Forgejo v8.0 was just released! Get it at https://forgejo.org/download/. 🚀
Forgejo v8.0 is available with new features (support for workflow dispatch, better defaults to avoid spam on new instances etc.), a new approach to UI and UX, careful upgrade of dependencies to improve stability and security. Foundation parts for ActivityPub based federation and data portability were merged, bringing these features closer to completion, but they're not available yet. ✨
Read more at https://forgejo.org/2024-07-release-v8-0/
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
The User Research effort that gained momentum two months ago continues with a new round of user testing sessions. It is key to build a roadmap.
Building blocks for both ActivityPub federation and data portability improvements were merged into the codebase. They are not yet used for any user visible feature but they are a stepping stone.
#Forgejo v7.0.1 was just released! This is a bug fix release.
We strongly recommend that all installations are upgraded to the latest version as soon as possible.
It fixes a LFS data corruption when running forgejo doctor check --all --fix or when [cron.gc_lfs].ENABLED=true is set (the default is false).
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.
#Forgejo v7.0 was just released! Get it at https://forgejo.org/download/. 🚀
Forgejo v7.0 is available with translations in Bulgarian, Esperanto, Filipino and Slovenian; SourceHut builds integration; support for the SHA-256 hash function in Git; source code search by default and more. It also is the first Long Term Support version. The adoption of semantic versioning is the reason for the version bump from v1.21 to v7.0 and is compatible with existing tools. ✨
Read more at https://forgejo.org/2024-04-release-v7-0/