Notices by Forgejo (forgejo@floss.social)

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/

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/

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

Forgejo may become a hard fork of Gitea; user research is on the way to figure out the scope of moderation in Forgejo instances; a new requirement for tests was added to the development workflow; the "You pushed on branch" user experience was improved; the migration of translations to Weblate began.

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

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

Learn about how Forgejo v1.19 came to be, the recent developments of Forgejo Actions and more.

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

You can skip this warning if you run a Forgejo instance using the binaries or container images downloaded from https://codeberg.org/forgejo/

⚠️ The tags on the Forgejo repository for v1.18.1-0, v1.18.2-0, v1.18.2-1, v1.18.3-0 and v1.18.3-1 were incorrectly set to the v1.19 development branch. The problem was fixed 11 February 2023 ~7am UTC.

If you built Forgejo from sources or got a package built by a third party using these tags, you are running v1.19.

A blog post will follow.

#Forgejo v1.18.2-0 was just released! This is a minor patch. 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.

After you upgrade from #Gitea to #Forgejo, don't forget to change your theme to our :forgejo: `forgejo` theme in your account preferences!

It's the default for new installs, but for existing installs users will keep their current theme unless they choose to change.

~ @caesar

Our first stable release, #Forgejo :forgejo: v1.18, has been published! 🎉 Upgrade now!

If you've been waiting to upgrade from #Gitea, now is your moment!

Read more at https://forgejo.org/2022-12-29-release-v1-18-0/

We're excited to announce the official launch of the #Forgejo project, a community-driven fork of #Gitea under the stewardship of @Codeberg.

Check out https://forgejo.org/2022-12-15-hello-forgejo/ to learn more, including the motivation for the fork, as well as Codeberg's announcement at https://blog.codeberg.org/codeberg-launches-forgejo.html

Come and get involved at https://codeberg.org/forgejo/forgejo or in our Matrix room https://matrix.to/#/#forgejo-chat:matrix.org . We aim to be a fully inclusive community and everyone's participation is welcomed.