Forgejo monthly report - May 2025

The monthly report is meant to provide a good overview of what has changed in Forgejo in the past month. If you would like to help, please get in touch in the chatroom or participate in the ongoing discussions.

Matrix chat room migration

We have been aware of problems with the Matrix chat room for some time. These problems manifested in profile information (usernames and profile pictures) being randomly reset, and member permissions being changed. This is due to state resets which are a known bug in Matrix.

Therefore, it was decided to recreate the Matrix room to solve these problems. This was done on 24 May. The old room is now officially deprecated, so please join the new room and continue communicating there. After a transition period, access to the old room will be restricted and it will become read-only.

You can find the new room under #forgejo-chat:matrix.org.

Releases

Forgejo v11.0.1 and v7.0.15

A security update was released on 2 May 2025 for the two current LTS versions, v11 and v7. This update resolves issues with uploading LFS files and a configured security key is now enforced for external accounts.

We strongly recommend that all Forgejo installations be upgraded to the latest version as soon as possible.

Helm chart

Several minor and patch versions of v12 have been released.

v12.5.1 contains a bug fix related to OAuth configuration. This fix was also backported to version 7 of the Helm chart and released with v7.1.12.

Minimum Git version

A discussion related to the minimum Git version required by Forgejo that began in March was concluded with a consensus. The benefits of this are that supporting newer Git features requires less backward compatibility fallbacks and also provides clearer information on which version is supported.
For Forgejo admins, this means that Forgejo will increase the required Git version with each LTS release (and only with LTS releases) to match the oldest Git version supported by Debian stable and Ubuntu LTS in ‘Standard Support’.

Federation

For a high-level overview, check out the federation roadmap.

Work on federated user activity continued this month. There has been progress on following a Forgejo user from GoToSocial. Progress was also made on the reverse: following a GoToSocial user from Forgejo.

Additionally, work on end-to-end testing was carried out. This is intended to ensure that the introduced federation capabilities can be automatically tested, thereby preventing potential regressions in the future.

User interface

This month was packed with housekeeping tasks, such as removing old and unused CSS and making general improvements to the hashboxes.

There were also quality-of-life changes, such as disabling autocapitalization and autocorrect for username fields and ensuring that the activity heatmap displays really old activity correctly, as well as adding messages to otherwise empty user cards.

Localization

This month, approximately 47 contributors were active, including 13 newcomers - an increase of 7 contributors and a decrease of 2 compared to April. Notably, this marks a higher engagement than in May 2024, indicating a healthy growth trend. However, year-to-year comparisons will become more meaningful in the coming months, as we were still in a ramp-up phase during this time last year.

Additionally, we are excited to announce the addition of a new team member for Finnish at the end of April. This has led to significant refactoring and an overall increase in completeness.

Sustainability

Work on the moderation feature, which is funded by NLnet, continued. Task F, which is part of the amended work plan, has been implemented. This gives users the option of reporting inappropriate content to the instance admin. There are still multiple open tasks for the moderation feature, but progress is steady.

Another part of the fund is allocated to documentation updates. As part of this, the Forgejo Actions documentation is being rewritten. The rewrite is currently in the review stage.

Infrastructure

Matrix moderation bot

Draupnir has been set up to simplify the fight against spam and other moderation tasks in Matrix rooms, which are part of the Forgejo space. It is a bot that offers tools for automated moderation as well as simplifications for manual moderation. The Forgejo Moderation Team manages the bot in accordance with the moderation process. Many thanks to the Draupnir team for their help and advice.

Crawlers hitting Forgejo instances

As already mentioned in the last blog post, Anubis has been deployed on Forgejo instances, which are part of the Forgejo infrastructure. As a result, some users had problems with their RSS client because they could not solve the presented challenges. The RSS routes have therefore been excluded from Anubis and are accessible again without any problems.

If you want to know more or have insights to share, check out the discussion “Crawlers hitting Forgejo instances - global abuse trend”.

Other

Codeberg enables quota feature

With Forgejo v9, a soft-quota feature was introduced. After some improvements were made in the meantime, like a quota overview in the web interface, Codeberg decided to enable the feature on their instance.
Read more about this in Codeberg’s dedicated blog post.

We Forge

Forgejo is a community of people who contribute in an inclusive environment. We forge on an equal footing, by reporting a bug, voicing an idea in the chatroom or implementing a new feature. The following list of contributors is intended to reflect this diversity and to acknowledge all the contributions made over the past month. If you are missing, please ask for an update.