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