runner

Files

T

History

silverwind 42858c61df fix: stop pruning the cached action ref on refresh (#1312 )

The action cache refresh fetched with `--prune` and the unqualified refspec `+<ref>:refs/runner/<hash>`. Git cannot map that ref back to a remote ref, so it deleted it on every other refresh. The first job after a branch or tag moved then failed with `cannot lock ref`, and a moved tag in a full clone could silently run its old commit. `--no-prune` fixes this and also overrides an inherited `fetch.prune`.

Fixes: https://gitea.com/gitea/runner/issues/1311
Reviewed-on: https://gitea.com/gitea/runner/pulls/1312
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: Zettat123 <39446+zettat123@noreply.gitea.com>

2026-10-14 13:15:01 +00:00

artifactcache

refactor(logging): add a logging abstraction and move the job logger onto it (#1295 )

2026-10-11 23:26:00 +00:00

artifacts

refactor(logging): add a logging abstraction and move the job logger onto it (#1295 )

2026-10-11 23:26:00 +00:00

common

fix: stop pruning the cached action ref on refresh (#1312 )

2026-10-14 13:15:01 +00:00

container

fix: give each docker proxy its own job label key (#1314 )