Forgejo

Beyond coding. We forge.

:forgejo: Website: https://forgejo.org
:codeberg: Source code: https://codeberg.org/forgejo/forgejo
:keyoxide: ID proofs (Keyoxide): https://keyoxide.org/[email protected]
:matrix: Matrix space: https://matrix.to/#/#forgejo:matrix.org

Public Key

npub12r320mcnpx7hnsr9v8ydwdk9eyqrlpm8usvspwzpd4hw8g5l9rdscrzz58

NIP-05 Address

[email protected]

Profile Code

nprofile1qqs9pc48aufsn0tecpjkrjxhxmzujqplsan7gxgqhpqk6mhr520j3kcprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aq6gefug

Publishing to

Author Public Key

npub12r320mcnpx7hnsr9v8ydwdk9eyqrlpm8usvspwzpd4hw8g5l9rdscrzz58

Show more details

Last Notes

2026-09-10 14:33:22 CEST

#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

2026-09-06 20:30:02 CEST

Forgejo Runner, the program executing workflows of continuous integration in #Forgejo, has been released in version 13.1.0. It features a new experimental plug-in API that is supposed to enable the community to integrate alternative job execution engines besides Docker and LXC. Forgejo Runner also no longer signals to commands that they are running within a terminal. https://forgejo.org/2026-09-runner-release-v131/
#ForgejoRunner #ForgejoActions #CI

2026-08-24 07:36:35 CEST

- reply

Could you provide some more information?
- From where do you try to download it (domain, downloadlink)
- How do you try to download it?
~ @npub16tr…5d24

2026-08-20 10:52:19 CEST

#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

2026-08-05 18:13:04 CEST

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

2026-07-31 18:30:12 CEST

- reply

Nein, aber @npub1fh7…ee83 hat gerade mit seiner Uptime zu kämpfen. https://status.codeberg.eu/status/codeberg
~ @npub1c7x…yhh5

2026-07-31 18:30:09 CEST

- reply

code.forgejo.org ist die offizielle Instanz von Forgejo für die Entwicklung von Forgejo bzw. zugehörige Projekte.
Die Releases wurden dorthin schon immer gespiegelt. Aufgrund einer Änderung in der Berechnung der Releases hat sich der Downloadlink geändert. Er ist aber valide und korrekt. :)
~ @npub16tr…5d24

2026-07-30 23:12:44 CEST

#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

2026-07-21 10:46:36 CEST

#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

2026-07-19 20:29:24 CEST

- reply

> a reproducer? wdym?
If you could create a repo on https://v16.next.forgejo.org/ where the translation is broken, because we cannot reproduce it atm.
~ @npub16tr…5d24

2026-07-19 18:24:25 CEST

- reply

Hello, we were unable to reproduce this on v16 or the latest state of the development branch (wirh 1, 2 and 800 as test values).
French as language is correct?
Do you have any customization on your instance?
Could you create a reproducer on https://v16.next.forgejo.org/ ?
~ @npub16tr…5d24

2026-07-16 13:21:45 CEST

- reply

Forgejo is pronounced like this: https://forgejo.org/static/forgejo.mp4
~ @npub16tr…5d24

2026-07-16 11:38:13 CEST

- reply

Have you checked your server time and the Forgejo logs?
It works for me and not aware about any breaking changes there...
~ @npub16tr…5d24

2026-07-16 11:17:11 CEST

- reply

This release got AI* and the automation directly did what they wanted...
~ @npub16tr…5d24
*Authorized Integrations

2026-07-16 11:12:16 CEST

#Forgejo 16.0.0 was just released! This is a security release.
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

2026-07-15 20:28:08 CEST

- reply

Thanks! Fixed it.
~ @npub16tr…5d24

2026-07-15 13:30:02 CEST

- reply

I'm sorry, I don't understand your question. What is missing for you?
The security announcement provides a step by step instruction to check if your deployment is affected by a CVE and if so how it can be mitigated via env or app.ini-config.
~ @npub16tr…5d24

2026-07-15 12:32:40 CEST

#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

2026-07-09 14:24:00 CEST

#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

2026-06-26 11:29:33 CEST

- reply

Time tracking isn't a new feature, it exists since a long time, but can be toggled via the server config: https://forgejo.org/docs/latest/admin/config-cheat-sheet/#service-service (`ENABLE_TIMETRACKING`).
But as far as I can see it is disabled on @npub1fh7…ee83 🤔 - as you mentioned them.
~ @npub16tr…5d24

2026-06-10 10:53:37 CEST

- reply

The instance was updated (followijg the release) and due to this for a short moment unavailable.
~ @npub16tr…5d24

2026-06-10 08:55:27 CEST

- reply

Sorry for this. We will take care of this in the future!
~ @npub16tr…5d24

2026-06-10 08:38:16 CEST

#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

2026-06-08 20:37:08 CEST

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.
https://forgejo.org/2026-05-monthly-report

2026-06-03 14:15:06 CEST

- reply

Yes, the docs mention CB as default source. code.forgejo.org is the official backup source (as also stated in the docs).
The release binaries should be restored.
~ @npub16tr…5d24

2026-06-03 13:43:18 CEST

- reply

Thanks for the ping.
There has been maintenance to remove old, outdated versions. It was not the intention to remove the binary files for the latest version.
Will redirect it to the right folks. In the meantime, please use code.forgejo.org :)
~ @npub16tr…5d24

2026-05-28 16:24:22 CEST

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

2026-05-26 17:45:31 CEST

- reply

Kommt vielleicht bald ;) https://codeberg.org/forgejo/forgejo/pulls/12666
~ @npub1c7x…yhh5

2026-05-20 12:01:00 CEST

- reply

Forgejo is written with a lower case "j". 😉 It has nothing to do with the name "Jo": https://forgejo.org/faq/#where-does-the-name-come-from
~ @npub16tr…5d24

2026-05-17 13:40:11 CEST

- reply

I'm sorry but this is not a he, it is a she. 😉 Jo is Forgejo's mascot:
https://codeberg.org/forgejo/governance/src/branch/main/branding/README.md#mascot
~ @npub16tr…5d24

2026-05-17 12:27:51 CEST

- reply

Forgejo is pronounced like this: https://forgejo.org/static/forgejo.mp4
(At least, that is the pronunciation the public is supposed to believe is the correct one. :pride_corgi: :rainbow_raised_fist: )
~ @npub16tr…5d24

2026-05-13 15:20:51 CEST

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.

2026-05-12 12:16:50 CEST

#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

2026-04-30 17:11:39 CEST

- reply

We believe these findings can be addressed publicly. The security team will open issues where approaches to implement new defensive measurements will be discussed, we believe there's no single answer and as such appreciate the opinion of other Forgejo contributors on this matter.
2/2

2026-04-30 17:11:28 CEST

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

2026-04-29 18:00:27 CEST

- reply

Check out @npub1fh7…ee83's configuration for its services using #iocaine by [@algernon](https://come-from.mad-scientist.club/@algernon ) https://codeberg.org/Codeberg-Infrastructure/scripted-configuration Documentation of iocaine you find at https://iocaine.madhouse-project.org/documentation/3/
Other instances use #Anubis. Also Forgejo's own instances are using that. Not a documentation, but you may find its configuration here: https://codeberg.org/forgejo/k8s-cluster/src/branch/main/flux/apps/forgejo-code/anubis
~ @npub1c7x…yhh5

2026-04-29 15:18:36 CEST

#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

2026-04-28 15:02:49 CEST

- reply

Hilft dir vielleicht Forgejos Dokumentation weiter? https://forgejo.org/docs/latest/user/api-usage/ Es gibt auch noch ein Forgejo-Kommandozeilenprogramm, das mit der Authentifizierung helfen kann: https://code.forgejo.org/forgejo/forgejo-curl
~ @npub1c7x…yhh5

2026-04-22 15:37:33 CEST

- reply

Tags can be protected, like branches, in the repository settings. See https://forgejo.org/docs/latest/user/protection/#protected-tags
~ @npub1c7x…yhh5

2026-04-21 09:30:55 CEST

- reply

Great that you managed!
~ @npub1c7x…yhh5

2026-04-21 09:25:20 CEST

- reply

Although it is not officially supported, you may get inspiration from this issue, collecting user experiences: https://codeberg.org/forgejo/discussions/issues/397
Please remember to have a proper backup before such database manipulations!
~ @npub1c7x…yhh5

2026-04-17 13:17:00 CEST

- reply

You can directly update from 13 to 15, Forgejo will handle all migrations.
But you should still check the release notes for v14 regarding breaking changes - and for sure don't forget the backup before upgrading :)
~ @npub16tr…5d24

2026-04-17 12:48:26 CEST

- reply

Don't be afraid ;) Make sure to have a proper backup before updating. https://forgejo.org/2026-04-release-v15-0/#upgrading
If you are still uncertain, you may also wait some days. v14.0 is still officially supported until end of April!
~ @npub1c7x…yhh5

2026-04-16 20:16:09 CEST

- reply

Thanks to everyone who took part in the Forgejo Release Party. See you next time and have fun with the new v15 release. :forgejo:
https://cdn.masto.host/floss/media_attachments/files/116/415/749/541/546/686/original/437286afa555d4c6.png

2026-04-16 18:34:03 CEST

- reply

The Forgejo Release Party is live. Feel free to stop by and say hello. We'll be discussing the release cycle, upcoming developments, and other Forgejo topics of interest.
~ Beowulf
https://cdn.masto.host/floss/media_attachments/files/116/415/347/998/501/031/original/df9f0fab1977efc6.png

2026-04-16 15:24:57 CEST

#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

2026-04-15 19:04:52 CEST

- reply

Enjoy editing Codemirror files with Codemirror on the forge, please!
PS: In case you want to improve how it is used within Forgejo, feel free to propose changes to the concerning files in https://codeberg.org/forgejo/forgejo/src/branch/forgejo/web_src/js/features or report issues at https://codeberg.org/forgejo/forgejo/issues. Thanks in advance!
~ @npub1c7x…yhh5

2026-04-15 14:04:23 CEST

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

2026-04-12 22:09:07 CEST

- reply

It is a huge topic which needs a lot of work, but work continues. It also affects the codebase in really basic areas which means reviewing takes more time too.
There is often in monthly reports a section e.g. here in the report from January: https://forgejo.org/2026-01-monthly-report/#federation
~ @npub16tr…5d24

2026-04-12 18:45:09 CEST

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

2026-04-11 23:14:21 CEST

- reply

Can you maybe clarify your question?
Go is the programming language in which Forgejo is written. So it is also a safety measurement to release a new version when the underlying programming language receives security patches.
~ @npub16tr…5d24

2026-04-10 22:50:41 CEST

- reply

You may find Go's release notes here: https://go.dev/doc/devel/release
~ @npub1c7x…yhh5

2026-04-10 15:28:44 CEST

#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

2026-04-05 14:45:18 CEST

- reply

Additionally there is https://codeberg.org/forgejo/forgejo/milestone/36366 which contains all changes, but also some changes which were backported to v14.
~ @npub16tr…5d24

2026-04-05 13:07:50 CEST

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

2026-03-30 14:43:15 CEST

- reply

Sounds a bit like the open feature request https://codeberg.org/forgejo/forgejo/issues/1410 for the first wish. The second one indeed is a goal for federation.
~ @npub1c7x…yhh5

2026-03-30 14:06:52 CEST

- reply

Thanks for reporting! Translation happens at https://translate.codeberg.org/engage/forgejo/
In the meantime, I proposed a fix for the string you reported: https://translate.codeberg.org/translate/forgejo/forgejo/nl/?checksum=6946e7abc9afe13c
Feel free to fix other weird strings, too. Contributions are always welcome!
~ @npub1c7x…yhh5

2026-03-30 00:37:40 CEST

- reply

By default, all “public” repositories including code, issues, etc. can be viewed by any guest without login. Why would you want a user to require signing in without the right to comment, etc.?
~ @npub1c7x…yhh5

2026-03-10 21:53:16 CET

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

2026-03-09 09:41:54 CET

#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

2026-03-02 08:58:04 CET

- reply

Merci beaucoup !
~ @npub1c7x…yhh5

2026-02-28 17:28:37 CET

- reply

Great that you managed! Do you want to share your experience and “delicate” steps here? https://codeberg.org/forgejo/discussions/issues/397
~ @npub1c7x…yhh5

2026-02-19 19:34:35 CET

- reply

Thanks for sharing! Feel free to add your solution to the list of pages in the delightful list https://codeberg.org/forgejo-contrib/delightful-forgejo#pages
~ @npub1c7x…yhh5

2026-02-19 09:06:00 CET

- reply

Some hints for customization you may find also here: https://forgejo.org/docs/latest/admin/advanced/customization/. You may take some inspiration from @npub1fh7…ee83's modifications here: https://codeberg.org/codeberg-infrastructure/forgejo/. On top of that, there were some attempts of more customization documentation within Forgejo here, but they never got merged: https://codeberg.org/forgejo/docs/pulls/1016
~ @npub1c7x…yhh5

2026-02-16 11:43:41 CET

- reply

That is one of Forgejo's long-time goals, which is actively worked on. See https://forgejo.org/faq/#what-about-forge-federation and https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md for the current status.
~ @npub1c7x…yhh5

2026-02-16 11:00:42 CET

- reply

Since version 12, Forgejo supports preview of 3D gLTF models, and this may be extended to other models …
https://forgejo.org/2025-07-release-v12-0/#gltf-viewer
But, for your usecase, it looks like that @npub1wfk…zv38 may indeed be the better choice.
~ @npub1c7x…yhh5

2026-02-16 10:46:54 CET

- reply

If the deletion is a repository deletion, nothing will happen, but the mirror will continue trying to mirror, but fail. But, if the deletion is via git force push with a new git history on the same repository, this deletion will be propagated.
~ @npub1c7x…yhh5

2026-02-14 20:14:40 CET

- reply

There is Renovate (https://docs.renovatebot.com/) which has support for forgejo: https://docs.renovatebot.com/modules/platform/forgejo/
Maybe this is what you are searching for?
~ @npub16tr…5d24

2026-02-05 16:16:09 CET

- reply

Indeed, this is not supported, but you might checkout https://codeberg.org/forgejo/discussions/issues/397. Feel free to share your experience there, too.
~ @npub1c7x…yhh5

2026-02-04 20:31:19 CET

- reply

There are no official Forgejo groups on Telegram.
Forgejo only has official groups on Matrix. The main Forgejo chat room is #forgejo-chat:matrix.org (the space with all rooms is #forgejo:matrix.org).
~ @npub16tr…5d24

2026-02-03 21:43:15 CET

- reply

The https://v15.next.forgejo.org/ instance updates daily to the latest commit on the development branch. You can experiment with it there or set up a local instance. Experimental daily builds can be found here: https://codeberg.org/forgejo-experimental/forgejo/releases
~ @npub16tr…5d24

2026-02-02 09:01:16 CET

- reply

The issue seems quite popular, but it needs someone to do the design work and implementation. Contributions are welcome (not only for this issue)!
~ @npub1c7x…yhh5

2026-01-31 15:27:13 CET

- reply

On the download page (https://forgejo.org/download/#installation-from-binary), under "Verify GPG signature," you can find our GPG key.
The release is signed using a subkey (with a one-year expiration time) from the master key.
More information can be found here: https://forgejo.org/docs/next/contributor/release/#release-signing-keys-management.
~ @npub16tr…5d24

2026-01-31 09:03:36 CET

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-monthly-report

2026-01-30 17:05:19 CET

- reply

instance administrators also have the option of customizing the behavior or enabling/disabling this feature.
For more information check the `DEFAULT_PUSH_CREATE_PRIVATE`, `ENABLE_PUSH_CREATE_USER` and `ENABLE_PUSH_CREATE_ORG` settings in the configuration file.
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#repository-repository
~ @npub16tr…5d24

2026-01-30 01:20:08 CET

- reply

Yes, it sounds also weird to me. Feel free to propose a change to the docs, if you want (Edit on bottom of the page leads to the source). ~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 19:37:55 CET

- reply

If you want more security by giving access only to one repository and maybe restrict it to reading, you can use deploy keys. They aren't very well documented currently, but basically you have to add a private SSH key as an action secret to the repository from which you want to deploy, and the public counterpart to the private goal repository. Some docs about these deploy keys (in another context) you find here: https://forgejo.org/docs/latest/user/repo-mirror/#mirror-via-ssh
~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 19:36:25 CET

- reply

You may use the checkout action. Likely, you'll need to use another user-wide access token for the private repositories.
https://code.forgejo.org/actions/checkout/#checkout-multiple-repos-private
~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 09:54:51 CET

#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

2026-01-24 12:12:26 CET

- reply

Check out also the open feature request for generic webhooks, https://codeberg.org/forgejo/forgejo/issues/4260, and the documented workaround by @npub1p09…m5vl: https://kitten.small-web.org/reference/#webhook
~ @npub1c7x…yhh5

2026-01-24 10:00:04 CET

- reply

I remember that someone, here in the Fediverse, posted about their working set-up, a while ago. I think it was using webhooks for that. https://forgejo.org/docs/latest/user/webhooks/
~ @npub1c7x…yhh5

2026-01-22 22:03:38 CET

- reply

The addition should be blocked if the key is not valid. If you can reproduce this, please open an issue at https://codeberg.org/forgejo/forgejo
~ @npub16tr…5d24

2026-01-20 00:54:36 CET

- reply

You may find an audio sample on our website ;)
https://forgejo.org/faq/#where-does-the-name-come-from
~ @npub1c7x…yhh5

2026-01-17 08:20:43 CET

- reply

The issues addressed by this Go update do not pose any risk to the system or data security of Forgejo deployments, only potential for denial of service attacks.

2026-01-17 08:20:36 CET

#Forgejo 11.0.10, 13.0.5 and 14.0.1 were just released!
All of them use an upgraded Go version with security fixes. We recommend that all installations are upgraded to the latest version as soon as possible.
Additionally, 14.0.1 includes a fix for a regression discovered in 14.0.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.
#forgejorelease

2026-01-15 15:09:33 CET

#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

2026-01-08 12:20:58 CET

#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

2026-01-06 11:49:08 CET

Some of us took a few days off between the years, but preparations for v14 are ongoing.
Therefore, we decided to skip the monthly report for December.
Nevertheless, you can look forward to the v14 release. Release preparations are actively underway and the release is scheduled for 15 January. If you want to help improve the release, feel free to test it. You can find more information here: https://forgejo.org/2025-09-monthly-report/#forgejo-v1300-release-candidates
The monthly report will return in early February, covering January and December.

2026-01-04 08:35:33 CET

- reply

You may give renovate a try, in the Forgejo development it is used for the dependency management with Forgejo.
https://www.mend.io/renovate/

2025-12-02 17:36:34 CET

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

2025-11-25 19:07:32 CET

- reply

Work is ongoing towards federated search across instances. See https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md#federated-repo-search-discovery-wip
That may allow to search within each federated instance for repositories on other federated instances.
~ @npub1c7x…yhh5

2025-11-25 18:27:22 CET

- reply

What is this search supposed to be searching for? Forgejo has code search, issue search, repo search, etc.
~ @npub1c7x…yhh5

2025-11-21 13:56:50 CET

#Forgejo 13.0.3 and 11.0.8 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

2025-11-16 09:07:07 CET

- reply

The next stable version release is planned for 16 January 2026 [1]. Security releases are announced as issues in a dedicated repository [2]. Next security release was rescheduled to 21 November to include security patches to dependencies.
[1] https://forgejo.org/docs/latest/admin/release-schedule/
[2] https://codeberg.org/forgejo/security-announcements/issues
~ @npub1c7x…yhh5

2025-11-08 14:04:46 CET

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.
https://forgejo.org/2025-10-monthly-report

2025-10-29 19:06:11 CET

- reply

0. Backup!
1. Upgrade to latest LTS or stable release
2. Enjoy!
See https://forgejo.org/docs/latest/admin/upgrade/
~ @npub1c7x…yhh5

2025-10-29 18:00:01 CET

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.

2025-10-26 07:52:55 CET

#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

2025-10-23 09:47:56 CEST

- reply

Codeberg has a small collection of user-contributed workflows for different needs:
https://codeberg.org/actions/meta/issues/10
And worth a look are the workflows used within Forgejo, e.g.,
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows
https://codeberg.org/forgejo/docs/src/branch/next/.forgejo/workflows
~ @npub1c7x…yhh5

2025-10-21 15:00:04 CEST

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.