Notices by Forgejo (forgejo@floss.social)

⚠️ 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.

https://forgejo.org/2025-01-monthly-update/

⚠️ 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 bug was fixed and the release rescheduled 16 January. 🤞

https://codeberg.org/forgejo/forgejo/milestone/8377

A regression was discovered on the release candidate for Forgejo v10.0.0. The release date was supposed to be 15 January and is postponed until this is fixed.

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.

https://forgejo.org/2024-11-monthly-update/

#Forgejo v9.0.2 and v7.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.

The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.

Forgejo is two years old and has been a lively human adventure, a story worth telling. A hackathon organized by Codeberg generated thousands of new translations. Forgejo v9.0.0 was published, as well as a security patch release which was backported to Forgejo v7. A kubernetes cluster was created to replace the current infrastructure, running Forgejo from the Helm Chart.

https://forgejo.org/2024-10-monthly-update/

While @Codeberg is working on fixing the outage, you can get Forgejo container images and binaries from an alternate location:

https://code.forgejo.org/forgejo/-/packages/container/forgejo/versions

https://code.forgejo.org/forgejo/forgejo/releases

#Forgejo v9.0 was just released! Get it at https://forgejo.org/download/. 🚀

It is the first version to be released under a copyleft license. Forgejo has early support for a soft-quota that can protect your server from high disk usage due to abuse. It also removes support for go-git, considered too hazardous for daily usage compared to Git. The translations saw an unprecedented number of improvements thanks to the hackathon organized by Codeberg.

Read more at https://forgejo.org/2024-10-release-v9-0/

Only three weeks to go for the next Forgejo release v9.0. We are excited to show you all the improvements we have worked on. But we are looking for your help to make the release a success.

Read https://forgejo.org/2024-09-preparing-v9/ to learn how you can help us with testing, translations, development and funding.

#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.

#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/

Forgejo is looking for input from #Forgejo administrators.

We are considering dropping support for using Microsoft SQL Server as a database that can be used with Forgejo. We would love to hear your input, especially those using it (if there are any 👀), on this matter. See our rationale and current discussion at https://codeberg.org/forgejo/discussions/issues/122, we're looking forward to your input on this matter.

The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.

Forgejo 7.0.0 release candidates are now available for testing at https://v7.next.forgejo.org or by downloading OCI images and binaries, updated daily. It will be the first LTS release, supported until July 2025. Four new translations that were added are Filipino, Esperanto, Slovenian and Bulgarian and the localization team keeps growing.

https://forgejo.org/2024-03-monthly-update/

#Forgejo v1.21.6-0 was just released! This is a security release.

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/2024-02-release-v1-21-6-0/.

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 forks its own path forward 🚀

Forgejo started as a soft fork of Gitea. Over time, it developed its own identity, adopted both development and governance practices - to ensure the stability, quality, and openness of the project - that made it more challenging to remain a soft fork. In early 2024, a decision was made to become a hard fork, and for Forgejo to forge its own path going forward. This post explains the consequences this decision will have.

https://forgejo.org/2024-02-forking-forward/