Pip cache step runs after install and key is never expanded #8

New Issue

2026-06-17T17:12:37+01:00

lyrathorpe commented

2026-06-17 17:12:37 +01:00

In .gitea/workflows/build-and-publish.yaml the "Cache pip dependencies" step runs AFTER "Install test dependencies", so the cache never accelerates the install it is meant to serve. Additionally the cache key is written as a YAML string "$RUNNER_OS-pip-..." where $RUNNER_OS is a shell variable that is never expanded in this context.

Fix:

Move the actions/cache step before the install step.
Use ${{ runner.os }} in the key instead of $RUNNER_OS.

Acceptance:

The cache is restored before dependencies are installed.
The cache key is OS-specific via the Actions expression.

In .gitea/workflows/build-and-publish.yaml the "Cache pip dependencies" step runs AFTER "Install test dependencies", so the cache never accelerates the install it is meant to serve. Additionally the cache key is written as a YAML string "$RUNNER_OS-pip-..." where $RUNNER_OS is a shell variable that is never expanded in this context. Fix: - Move the actions/cache step before the install step. - Use ${{ runner.os }} in the key instead of $RUNNER_OS. Acceptance: - The cache is restored before dependencies are installed. - The cache key is OS-specific via the Actions expression.

lyrathorpe added the ci label 2026-06-17 17:12:37 +01:00

lyrathorpe referenced this issue from a commit

2026-06-17 17:22:32 +01:00

ci: cache pip before install and fix cache key OS expansion

lyrathorpe referenced a pull request that will close this issue

2026-06-17 17:23:01 +01:00

Cache pip before install and fix cache key expansion #12

lyrathorpe closed this issue

2026-06-17 17:33:38 +01:00

lyrathorpe referenced this issue from a commit

2026-06-17 17:33:39 +01:00

Cache pip before install and fix cache key expansion (#12)