git.fristy.net/actions/runner-images (tag ubuntu-latest = Ubuntu 26.10) already ships the toolchain we were re-downloading on every run:
tool
version in image
previously fetched by
node
26.13.0 (also in RUNNER_TOOL_CACHE)
actions/setup-node
pnpm
12.16.1
pnpm/action-setup
python3 + pipx
3.14.8 / 1.15.0
actions/setup-python
Removed all three steps. Verified against the actual image:
pnpm install --frozen-lockfile passes with the image toolchain (1m05s, pnpm 12.16.1).
pipx run --spec desloppify desloppify --version works on the image's Python 3.14.8.
setup-python also asked for 3.15, which has no build for the Ubuntu 26.10 runner image (The version '3.15' with architecture 'x64' was not found for Ubuntu 26.10) — that is what turned Code Health red on every run since the runner image moved to 26.10.
The pnpm store cache step is kept; only the three setup steps are gone.
`git.fristy.net/actions/runner-images` (tag `ubuntu-latest` = Ubuntu 26.10) already ships the toolchain we were re-downloading on every run:
| tool | version in image | previously fetched by |
|---|---|---|
| node | 26.13.0 (also in `RUNNER_TOOL_CACHE`) | `actions/setup-node` |
| pnpm | 12.16.1 | `pnpm/action-setup` |
| python3 + pipx | 3.14.8 / 1.15.0 | `actions/setup-python` |
Removed all three steps. Verified against the actual image:
- `pnpm install --frozen-lockfile` passes with the image toolchain (1m05s, pnpm 12.16.1).
- `pipx run --spec desloppify desloppify --version` works on the image's Python 3.14.8.
`setup-python` also asked for `3.15`, which has no build for the Ubuntu 26.10 runner image (`The version '3.15' with architecture 'x64' was not found for Ubuntu 26.10`) — that is what turned `Code Health` red on every run since the runner image moved to 26.10.
The pnpm store cache step is kept; only the three setup steps are gone.
node 26.13.0, pnpm 12.16.1, corepack and python3+pipx are baked into git.fristy.net/actions/runner-images, so setup-node, pnpm/action-setup and setup-python only re-downloaded them (and burned the shared GitHub API quota). setup-python also asked for 3.15, which has no build for the Ubuntu 26.10 runner image, breaking the Code Health job.
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.
git.fristy.net/actions/runner-images(tagubuntu-latest= Ubuntu 26.10) already ships the toolchain we were re-downloading on every run:RUNNER_TOOL_CACHE)actions/setup-nodepnpm/action-setupactions/setup-pythonRemoved all three steps. Verified against the actual image:
pnpm install --frozen-lockfilepasses with the image toolchain (1m05s, pnpm 12.16.1).pipx run --spec desloppify desloppify --versionworks on the image's Python 3.14.8.setup-pythonalso asked for3.15, which has no build for the Ubuntu 26.10 runner image (The version '3.15' with architecture 'x64' was not found for Ubuntu 26.10) — that is what turnedCode Healthred on every run since the runner image moved to 26.10.The pnpm store cache step is kept; only the three setup steps are gone.