Gitea

We are proud to present the release of Gitea version 1.19.4. We highly encourage users to update to this version for some important bug-fixes. We have merged 62 pull requests to release this version. You can download one of our pre-built binaries ... [More] from our downloads page - make sure to select the correct platform! For further details on how to install, follow our installation guide. We would also like to thank all of our supporters on Open Collective who are helping to sustain us financially. Have you heard? We now have a swag shop! 👕 🍵 [Less]

We are proud to present the release of Gitea version 1.19.3. We highly encourage users to update to this version for some important bug-fixes. We have merged 8 pull requests to release this version. In this release, we use golang 1.20.4 to fix ... [More] CVE-2023-24539, CVE-2023-24540, and CVE-2023-29400 . You can download one of our pre-built binaries from our downloads page - make sure to select the correct platform! For further details on how to install, follow our installation guide. We would also like to thank all of our supporters on Open Collective who are helping to sustain us financially. Have you heard? We now have a swag shop! 👕 🍵 [Less]

Gitea 1.19.0 brings several improvements to issue and pull request management, making it more efficient across different repositories. In this article, we’ll discuss three notable new features: Organization/User Level Projects, Scoped Labels, and Advanced Label Templates. Learn how these updates can help optimize your development workflow.

We are proud to present the release of Gitea version 1.19.2. We highly encourage users to update to this version for some important bug-fixes. We have merged 42 pull requests to release this version. In this release, we introduced a database ... [More] conversion tool via ./gitea admin convert to help convert MSSQL columns from VARCHAR to NVARCHAR. Any Gitea instances set up with MSSQL before 1.13.0 may need this tool. This release also includes an update to the go-redis library used by Gitea which adds support for redis-cluster (in combination with #23869 from the 1.19.1 release). Gitea configured with redis-cluster allows for high-availability in Kubernetes environments. (PS: We are currently working on switching to redis-cluster (from memcached) in the helm chart and providing detailed HA documentation - stay tuned!) Thanks to @KN4CK3R for reporting both security issues patched in this release, and thanks to him and @lunny for the subsequent fixes! You can download one of our pre-built binaries from our downloads page - make sure to select the correct platform! For further details on how to install, follow our installation guide. We would also like to thank all of our supporters on Open Collective who are helping to sustain us financially. Have you heard? We now have a swag shop! 👕 🍵 [Less]

In working towards maintaining an LTS version of Gitea, one of the blockers was to be able to efficiently backport pull requests, for bug fixes and other changes. One of Gitea’s maintainers, yardenshoham, in an effort to improve their development ... [More] workflow created a tool to help automate backports. A side-effect of this effort is that this tool can not only be used to backport just for his pull-requests, but most pull requests that need a backport too. [Less]

Gitea’s CI system, Gitea Actions, was recently released in version 1.19.0. Gitea Actions is an internal CI/CD system, offering near compatibility with GitHub Actions. One key difference is that Gitea supports both Go and JavaScript actions, while ... [More] GitHub only supports JavaScript actions natively (though you can use any programming language for Docker container actions). Go actions provide a way for gophers who are not familiar with JavaScript to create native actions. [Less]

We are proud to present the release of Gitea version 1.19.1. We highly encourage users to update to this version for some important bug-fixes. We have merged 95 pull requests to release this version. ❗ If you are using actions.actions in ... [More] DISABLED_REPO_UNITS or DEFAULT_REPO_UNITS, it will be treated as an invalid unit key. It has been changed to repo.actions for consistency. If you haven’t placed it there explicitly, no action is required. While Gitea aims for stability in already released versions, we decided to release this breaking change in 1.19.1 because Gitea Actions are still experimental and this option was previously undocumented, so we expect that a vast majority of users are likely unaffected. You can download one of our pre-built binaries from our downloads page - make sure to select the correct platform! For further details on how to install, follow our installation guide. We would also like to thank all of our supporters on Open Collective who are helping to sustain us financially. Have you heard? We now have a swag shop! 👕 🍵 [Less]

As of 1.19.0, Gitea supports asciicast! Maybe this is the first time you’ve heard of asciicast. This blog will teach you how to use asciicast, and how it relates to Gitea. What is asciicast? As programmers, we often work with terminals and the ... [More] command line. Sometimes, we encounter unfamiliar commands. Othertimes, the output of commands is not what we expect. In both these cases, we need to show someone else what we did and what the output is. [Less]

Gitea 1.19.0 includes a new feature called Gitea Actions. This is a built-in CI system of Gitea, similar and compatible to GitHub Actions. This blog will explain some details about Gitea Actions, including how to use it and how it works. It should be ... [More] noted that the information presented pertains to the current situation, and may become outdated in the future. [Less]

The documentation site has hosted the nightly documentation for the project for a long time now. This works in the majority of cases when someone is referring to the docs to support their Gitea instance. However, sometimes when a highly anticipated ... [More] feature is merged into the development branch and the documentation is included, users who may not keep up with the release cycle run into problems when attempting to activate or configure functionality that isn’t yet in a stable release. [Less]