The current the workflow doesn't actually pass a .python-version matrix to to setup-uv or uv sync (no python-version input, no uv python pin) - i.e. all 12 jobs actually just testing whatever uv picks by default (likely the .python-version 3.12.3, or the latest available?) - basically the same bug that was found in this PR for isp-trace-parser.
Addressing this probably good opportunity to update python versions (maybe introduce nox here too). Currently python 3.13/3.14 are allowed ( requires-python = >= 3.9 ) but CI tests only 3.9, 3.10, 3.11, and 3.12 (.. and 3.9 EOL).
The current the workflow doesn't actually pass a
.python-versionmatrix to to setup-uv or uv sync (no python-version input, no uv python pin) - i.e. all 12 jobs actually just testing whatever uv picks by default (likely the .python-version 3.12.3, or the latest available?) - basically the same bug that was found in this PR forisp-trace-parser.Addressing this probably good opportunity to update python versions (maybe introduce nox here too). Currently python 3.13/3.14 are allowed (
requires-python = >= 3.9) but CI tests only 3.9, 3.10, 3.11, and 3.12 (.. and 3.9 EOL).