Forgejo v1.19.0-2 was released. It comes with an extensive user guide, derived for the most part from the Codeberg documentation. The new admin guide covers upgrades and configuration of Forgejo instances.
The most prominent new features are:
- Actions: an experimental CI/CD, although not ready for real world usage, is present and can be used to run a demo.
- Incoming emails: you can now set up Forgejo to receive incoming emails. When enabled, it is possible to reply to an email notification from Forgejo and (i) add a comment to an issue or a pull request, (ii) unsubscribe to notifications.
- Scoped access tokens: Forgejo access token, used with the API, can now have a “scope” that limits what it can access.
- Package registries now support Cargo, Conda and Chef.
Read more in the Forgejo v1.19.0-2 release notes
Carefully read the breaking changes section of the release notes.
The actual upgrade process is as simple as replacing the binary or container image
with the corresponding Forgejo binary
or container image.
If you’re using the container images, you can use the
to stay up to date with the latest
1.19.x point release automatically.
Make sure to check the Forgejo upgrade documentation for recommendations on how to properly backup your instance before the upgrade. It also covers upgrading from Gitea, as far back as version 1.2.0. Forgejo includes all of Gitea v1.19, with improvements.
The Forgejo instances built from an incorrect tag can safely be upgraded.
If you have any feedback or suggestions for Forgejo, we’d love to hear from you! Open an issue on our issue tracker for feature requests or bug reports, find us on the Fediverse, or drop into our Matrix space (main chat room) and say hi!