The routine for upgrading Gitea can be found here in Norwegian, but in short :
⚠️ Do not upgrade to the first patch versionx.x.0, wait until the major version is stable
⚠️ Ensure all custom files (configuration, templates, and locales) are up to date, as they may change between releases
Ensure that our custom configuration is up to date by comparing it with the app.example.ini file provided by Gitea (see: https://github.com/go-gitea/gitea/blob/release/v{VERSION}/custom/conf/app.example.ini).
Ensure that our custom templates are up to date by comparing them with the templates from Gitea (see: https://github.com/go-gitea/gitea/tree/release/v{VERSION}/templates).
The files located in ./files/locale/base are the original translations from Gitea. They must be updated when upgrading Gitea to a newer version.
-
Update locale_en-US.ini using https://github.com/go-gitea/gitea/tree/release/v{VERSION}/options/locale/locale_en-US.ini.
-
Update locale_nb-NO.ini using Crowdin. Crowdin only contains the latest version, so you must ensure that the keys match the version your are upgrading to.
⚠️ Do not make custom changes to these files, as they will be overwritten during future upgrades. If you need to make changes, you can either :
- Submit your changes via Crowdin for the Norwegian version, and download the updated file that includes your changes
- Add custom translations to our custom locale files (see below)
The files located in ./files/locale/custom are our custom locales for Studio. Ensure that all keys in these files are still in use when upgrading Gitea to a newer version.
Reload config:
docker rm --force studio-repositories
docker rmi --force repositories:latest
docker compose -f ../compose.yaml up -d