The runner serves the cache service v2 API alongside v1, on by default and working with external_server. To reach it, the official cache actions are patched before they run, while unrecognised actions run untouched against v1. The same patch fixes the official artifact actions, so actions/upload-artifact and actions/download-artifact v4.4.0 and newer work as published and the gitea-upload-artifact fork can be dropped. The v2 API can be disabled via cache.v2: false in the configuration.
Two daemons started from the same .runner file looked like one runner to Gitea and cancelled each other's jobs. The file is now locked at startup, so every runner needs its own runner.file and its own registration.
A workflow could use container.options to reach the runner host, for example by joining its process namespace, even with privileged mode off. Those options are now dropped with a warning, turn on container.privileged to keep them working.
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| [gitea/runner](https://gitea.com/gitea/runner) | major | `2.3.0` → `3.0.1` |
---
### Release Notes
<details>
<summary>gitea/runner (gitea/runner)</summary>
### [`v3.0.1`](https://gitea.com/gitea/runner/releases/tag/v3.0.1)
[Compare Source](https://gitea.com/gitea/runner/compare/v3.0.0...v3.0.1)
#### Bug fixes
- Coerce every expression value kind to a string and drop the `format()` panic — <https://gitea.com/gitea/runner/pulls/1135>
#### Dependencies
- Drop `Masterminds/semver` and `pkg/errors`, re-sync the `docker/cli` copies — <https://gitea.com/gitea/runner/pulls/1132>
**Full changelog**: <https://gitea.com/gitea/runner/compare/v3.0.0...v3.0.1>
### [`v3.0.0`](https://gitea.com/gitea/runner/releases/tag/v3.0.0)
[Compare Source](https://gitea.com/gitea/runner/compare/v2.3.0...v3.0.0)
#### ⚠️ Breaking changes
##### Cache service v2 (<https://gitea.com/gitea/runner/pulls/1110>)
The runner serves the cache service v2 API alongside v1, on by default and working with `external_server`. To reach it, the official cache actions are patched before they run, while unrecognised actions run untouched against v1. The same patch fixes the official artifact actions, so `actions/upload-artifact` and `actions/download-artifact` v4.4.0 and newer work as published and the `gitea-upload-artifact` fork can be dropped. The v2 API can be disabled via `cache.v2: false` in the configuration.
##### Only one runner process per registration file (<https://gitea.com/gitea/runner/pulls/1099>)
Two daemons started from the same `.runner` file looked like one runner to Gitea and cancelled each other's jobs. The file is now locked at startup, so every runner needs its own `runner.file` and its own registration.
##### Container options that reach the host now require privileged mode (<https://gitea.com/gitea/runner/pulls/1058>)
A workflow could use `container.options` to reach the runner host, for example by joining its process namespace, even with privileged mode off. Those options are now dropped with a warning, turn on `container.privileged` to keep them working.
#### Features
- Add cache service v2 and toolkit patches (<https://gitea.com/gitea/runner/pulls/1110>)
- Add job hooks `runner.hooks.job_started` and `runner.hooks.job_completed` (<https://gitea.com/gitea/runner/pulls/1111>)
- Propagate proxy variables to jobs, services and builds (<https://gitea.com/gitea/runner/pulls/1112>)
- Mask secrets that reach the log in an encoded form (<https://gitea.com/gitea/runner/pulls/1108>)
#### Bug fixes
- Resolve symlinked container paths before building tar entries (<https://gitea.com/gitea/runner/pulls/1130>)
- Stop leaking per-job docker networks (<https://gitea.com/gitea/runner/pulls/1124>)
- Fix panics, enable the `forcetypeassert` lint (<https://gitea.com/gitea/runner/pulls/1123>)
- Allow relocating the tool cache and mounting over runner paths (<https://gitea.com/gitea/runner/pulls/1122>)
- Strip leading slash from mkdir tarball in `CopyTarStream` (<https://gitea.com/gitea/runner/pulls/1129>)
**Full changelog**: <https://gitea.com/gitea/runner/compare/v2.3.0...v3.0.0>
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC41LjAiLCJ1cGRhdGVkSW5WZXIiOiI0NC43LjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
2.3.0→3.0.1Release Notes
gitea/runner (gitea/runner)
v3.0.1Compare Source
Bug fixes
format()panic — https://gitea.com/gitea/runner/pulls/1135Dependencies
Masterminds/semverandpkg/errors, re-sync thedocker/clicopies — https://gitea.com/gitea/runner/pulls/1132Full changelog: https://gitea.com/gitea/runner/compare/v3.0.0...v3.0.1
v3.0.0Compare Source
⚠️ Breaking changes
Cache service v2 (https://gitea.com/gitea/runner/pulls/1110)
The runner serves the cache service v2 API alongside v1, on by default and working with
external_server. To reach it, the official cache actions are patched before they run, while unrecognised actions run untouched against v1. The same patch fixes the official artifact actions, soactions/upload-artifactandactions/download-artifactv4.4.0 and newer work as published and thegitea-upload-artifactfork can be dropped. The v2 API can be disabled viacache.v2: falsein the configuration.Only one runner process per registration file (https://gitea.com/gitea/runner/pulls/1099)
Two daemons started from the same
.runnerfile looked like one runner to Gitea and cancelled each other's jobs. The file is now locked at startup, so every runner needs its ownrunner.fileand its own registration.Container options that reach the host now require privileged mode (https://gitea.com/gitea/runner/pulls/1058)
A workflow could use
container.optionsto reach the runner host, for example by joining its process namespace, even with privileged mode off. Those options are now dropped with a warning, turn oncontainer.privilegedto keep them working.Features
runner.hooks.job_startedandrunner.hooks.job_completed(https://gitea.com/gitea/runner/pulls/1111)Bug fixes
forcetypeassertlint (https://gitea.com/gitea/runner/pulls/1123)CopyTarStream(https://gitea.com/gitea/runner/pulls/1129)Full changelog: https://gitea.com/gitea/runner/compare/v2.3.0...v3.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
cba49d60abto6d3ebdad39