ci: remove the inert nox/uv cache step from test-python

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.

[prql-bot]

The Cache uv and Nox step in test-python has never cached anything: both paths it names are wrong, so every restore misses and every save is skipped with a path-validation warning. This removes that step and the Compute pyproject.toml hash step that only fed its key. astral-sh/setup-uv already caches uv's cache directory with a correct per-platform key, and nox recreates its virtualenvs on every run, so nothing is lost.

Verified against the last two nightly runs: the nox-uv-… key missed on all three OSes on both days, and the post step logged Path(s) specified in the action for caching do(es) not exist.

Evidence and mechanism

Both cached paths are wrong:

• .nox — the run command is nox -s tests typing -f prqlc/bindings/prqlc-python/noxfile.py. nox chdirs to the noxfile's directory, so the env dir is created at prqlc/bindings/prqlc-python/.nox, not the repo-root .nox the cache step names. The 2026-08-29 ubuntu job shows both: CWD /home/runner/work/prql/prql/prqlc/bindings/prqlc-python and nox > Creating virtual environment (uv) using python3.10 in .nox/tests-3-10.
• ~/.cache/uv — astral-sh/setup-uv@v7 sets UV_CACHE_DIR=/home/runner/work/_temp/setup-uv-cache, visible in that job's step env. uv never writes to ~/.cache/uv here.

With neither path present, the post step logs:

[warning]Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

so no cache is ever written, and the restore correspondingly misses every time. Across the two most recent scheduled 3-OS runs — 33248713260 (2026-08-29) and 33181607218 (2026-08-28) — all six jobs logged:

Cache not found for input keys: nox-uv-ed1962a15f136f9bb5a100fd443a9c9490a8abdab41491d25d1ba2f875b5273b

Note the key is byte-identical across ubuntu, macOS, and Windows: it has no ${{ runner.os }} component, unlike the repo's elixir cache keys. Rather than add the OS component, this removes the step, because neither path is worth caching once the paths are corrected:

• ~/.cache/uv would duplicate setup-uv's own cache, which is working — the same jobs log Cache hit for: setup-uv-2-x86_64-unknown-linux-gnu-… and uv cache saved with key: setup-uv-2-…, keyed per platform, python version, and uv version.
• .nox is recreated on every run regardless: noxfile.py sets nox.options.reuse_existing_virtualenvs = False, and the logs confirm a fresh Creating virtual environment line for each of the four sessions.

No regression test: this is a CI workflow change with no code under test. The check is the test-python / test job itself — it should keep passing, and its post step should no longer emit the path-validation warning.