The cache adapter implements only the v1 _apis/artifactcache routes
(crates/runner-cache-github-actions/src/server.rs:58-64). Buildx 0.35 and actions/cache@v4 speak the newer twirp backend and pick it when ACTIONS_RUNTIME_TOKEN and ACTIONS_RESULTS_URL are set — which the runner
already sets (context/environment/names.rs:155-158).
Consequences today:
--cache-to type=gha cannot be used, so release builds cache through the
registry instead (.gitea/workflows/build-image.yml);
artifact and cache actions are pinned to @v3 in the compatibility suite.
Serving v2 alongside v1 removes both workarounds.
The cache adapter implements only the v1 `_apis/artifactcache` routes
(`crates/runner-cache-github-actions/src/server.rs:58-64`). Buildx 0.35 and
`actions/cache@v4` speak the newer twirp backend and pick it when
`ACTIONS_RUNTIME_TOKEN` and `ACTIONS_RESULTS_URL` are set — which the runner
already sets (`context/environment/names.rs:155-158`).
Consequences today:
- `--cache-to type=gha` cannot be used, so release builds cache through the
registry instead (`.gitea/workflows/build-image.yml`);
- artifact and cache actions are pinned to `@v3` in the compatibility suite.
Serving v2 alongside v1 removes both workarounds.
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.
The cache adapter implements only the v1
_apis/artifactcacheroutes(
crates/runner-cache-github-actions/src/server.rs:58-64). Buildx 0.35 andactions/cache@v4speak the newer twirp backend and pick it whenACTIONS_RUNTIME_TOKENandACTIONS_RESULTS_URLare set — which the runneralready sets (
context/environment/names.rs:155-158).Consequences today:
--cache-to type=ghacannot be used, so release builds cache through theregistry instead (
.gitea/workflows/build-image.yml);@v3in the compatibility suite.Serving v2 alongside v1 removes both workarounds.