Upgrade Gitea Actions runner to 5.4.0 #697

2026-11-05T10:45:51Z

raucao commented

2026-11-05 10:45:51 +00:00

Upgrades the Gitea Actions runner from 5.2.4 to 5.4.0. No config.yaml changes were required.

5.3.0 scopes cache entries by ref, like GitHub: a job restores from its own ref, then the base branch, then the repository's default branch, and writes only to its own ref. Existing (unscoped) caches therefore start out cold once after the upgrade. 5.3.0 also adds GITEA_* aliases for the built-in GITHUB_* environment variables and updates dependencies for CVE-2026-78661.

5.4.0 adds Windows and FreeBSD support, runner.ca_file for trusting a private CA, and container.volumes; it signs release checksums and fixes large cache uploads, concurrent Dockerfile actions, and git-lfs checkouts on git-lfs versions before 3.8.0.

This also re-establishes 5.4.0 on gitea-2. The node was still running 5.2.2 because a converge from a branch that predated the previous upgrade downgraded it. Gitea reports the version sent on each heartbeat, so the runners updated on restart. The checksum was verified against the published binary and checksums.txt.

Upgrades the Gitea Actions runner from 5.2.4 to 5.4.0. No `config.yaml` changes were required. 5.3.0 scopes cache entries by ref, like GitHub: a job restores from its own ref, then the base branch, then the repository's default branch, and writes only to its own ref. Existing (unscoped) caches therefore start out cold once after the upgrade. 5.3.0 also adds `GITEA_*` aliases for the built-in `GITHUB_*` environment variables and updates dependencies for CVE-2026-78661. 5.4.0 adds Windows and FreeBSD support, `runner.ca_file` for trusting a private CA, and `container.volumes`; it signs release checksums and fixes large cache uploads, concurrent Dockerfile actions, and git-lfs checkouts on git-lfs versions before 3.8.0. This also re-establishes 5.4.0 on gitea-2. The node was still running 5.2.2 because a converge from a branch that predated the previous upgrade downgraded it. Gitea reports the version sent on each heartbeat, so the runners updated on restart. The checksum was verified against the published binary and `checksums.txt`.

raucao added 1 commit 2026-11-05 10:45:51 +00:00

Upgrade Gitea Actions runner to 5.4.0 3d08572896

Runner 5.2.4 -> 5.4.0. No config.yaml changes were required.

5.3.0 scopes cache entries by ref, like GitHub: a job restores from its own
ref, then the base branch, then the repository's default branch, and writes
only to its own ref. Existing (unscoped) caches therefore start out cold once
after the upgrade. 5.3.0 also adds GITEA_* aliases for the built-in GITHUB_*
environment variables and updates dependencies for CVE-2026-78661.

5.4.0 adds Windows and FreeBSD support, runner.ca_file for trusting a private
CA, and container.volumes; it signs release checksums and fixes large cache
uploads, concurrent Dockerfile actions, and git-lfs checkouts on git-lfs
versions before 3.8.0.

The node was still running 5.2.2 because a converge from a branch that
predated the previous upgrade downgraded it. This re-establishes 5.4.0 on
gitea-2; Gitea reports the version sent on each heartbeat, so the runners
updated on restart. Checksum verified against the published binary and
checksums.txt.

raucao added the

service

gitea

kredits-1 ops labels 2026-11-05 10:46:17 +00:00

raucao merged commit 97aaa4d9ab into master

2026-11-05 10:46:27 +00:00

raucao deleted branch chore/upgrade_gitea-runner

2026-11-05 10:46:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#697