fix(ci): hardcode RUNNER_TOOL_CACHE path - runner context unbound in job env #92

Merged

nrupard merged 1 commit from fix/e2e-runner-toolcache into main

2026-06-05 16:18:59 +02:00

nrupard commented

2026-06-05 16:18:47 +02:00

Owner

The previous attempt set RUNNER_TOOL_CACHE to ${{ runner.temp }}/toolcache, which Forgejo's workflow schema rejects: the runner context is not yet bound when job-env is evaluated, so the workflow fails to load with "Unknown Variable Access runner".

Switch to a fixed /tmp/toolcache. /tmp is writable on every runner and the prepare-cache step still mkdir -p's it before setup-node runs.

#PMS-140

The previous attempt set RUNNER_TOOL_CACHE to ${{ runner.temp }}/toolcache, which Forgejo's workflow schema rejects: the `runner` context is not yet bound when job-env is evaluated, so the workflow fails to load with "Unknown Variable Access runner". Switch to a fixed /tmp/toolcache. /tmp is writable on every runner and the prepare-cache step still mkdir -p's it before setup-node runs. #PMS-140

nrupard added 1 commit

2026-06-05 16:18:47 +02:00

fix(ci): hardcode RUNNER_TOOL_CACHE path - runner context unbound in job env

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / fmt + clippy + compile + tests (pull_request) Failing after 2m0s

Details

020631b3b0

The previous attempt set RUNNER_TOOL_CACHE to ${{ runner.temp }}/toolcache, which Forgejo's workflow schema rejects: the `runner` context is not yet bound when job-env is evaluated, so the workflow fails to load with "Unknown Variable Access runner".

Switch to a fixed /tmp/toolcache. /tmp is writable on every runner and the prepare-cache step still mkdir -p's it before setup-node runs.

#PMS-140