pyproject.toml declares requires-python = ">=3.13", but every CI job resolves to CPython 3.14.6 — ci.yml sets no python-version and no matrix. Python 3.13 is a supported target that is never built, tested or audited. PR #119 also introduced a resolution-markers split on 3.14 in uv.lock; today no package forks to a different version across those branches (verified in review), but the split makes a future divergence possible without CI noticing. Add a python-version: ["3.13", "3.14"] matrix to at least the test and security jobs, or raise requires-python to >=3.14 if 3.13 support is not intended.
From PR #119 review.
pyproject.toml declares requires-python = ">=3.13", but every CI job resolves to CPython 3.14.6 — ci.yml sets no python-version and no matrix. Python 3.13 is a supported target that is never built, tested or audited. PR #119 also introduced a resolution-markers split on 3.14 in uv.lock; today no package forks to a different version across those branches (verified in review), but the split makes a future divergence possible without CI noticing. Add a python-version: ["3.13", "3.14"] matrix to at least the test and security jobs, or raise requires-python to >=3.14 if 3.13 support is not intended.
From PR #119 review.