Skip to content

CI test matrix runs every Python version on 3.14 (.python-version overrides setup-python) #384

Open

Description

@jwulf

Problem

The CI test matrix (3.10 … 3.14) does not test the versions it names. actions/setup-python installs the matrix version, but uv sync picks the interpreter from .python-version (3.14), so every matrix job runs on 3.14:

test (3.10)  Set up Python 3.10  python-version: 3.10
test (3.10)  Install dependencies  Using CPython 3.14.4 interpreter at: /usr/bin/python3.14

(run 43146776855, job test (3.10))

So the SDK's declared floor (requires-python >=3.10) and 3.11–3.13 are never tested in CI.

Constraint

The generator (openapi-python-client ≥0.29.1) needs Python ≥3.11, but the SDK must keep supporting 3.10. The fix must therefore generate on ≥3.11 and run the acceptance and integration tests against the generated SDK on the matrix interpreter. One way: generate once on the pinned version, then uv sync --python ${{ matrix.python-version }} (or set UV_PYTHON) in an environment without the generator, and test.

Bug class: test / build / CI infrastructure.

Activity

  1. added
    bugSomething isn't working as documented or intended
    affects/mainBug present on main (the next release / alpha)
    affects/stableBug present in a released stable line (stable/N branches)
    severity/highCore feature broken; workaround is painful
    found-by/ciCaught by the repo's own build, tests, generation-drift or publish pipeline
    on Nov 12, 2026
  2. self-assigned this
    on Nov 12, 2026
  3. jwulf commented on Nov 12, 2026

    @jwulf
    MemberAuthor

    Taking this. main: #398 (ci/release-gates, draft; it also carries the #389 R1 smoke gate, as separate commits). It depends on #392 and #395, since the real 3.10 leg and the smoke gate already catch those two bugs. Backports to stable/10 and stable/9 follow on ci/real-matrix-10 and ci/real-matrix-9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

affects/mainBug present on main (the next release / alpha)affects/stableBug present in a released stable line (stable/N branches)bugSomething isn't working as documented or intendedfound-by/ciCaught by the repo's own build, tests, generation-drift or publish pipelineseverity/highCore feature broken; workaround is painful

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions