Repository navigation
ci: the gates and the full suite run on Python 3.14, not the newest supported version #1661
Closed as not planned
Description
Problem. Jobs that run on a single interpreter still pin 3.14, though the newest supported version has been 3.15 since #1645. On main (edada31dd):
unit-tests.yml:1482-1492,Gate (full suite, Python 3.14), plus:1297,:1351and:1461- the coverage leg (
unit-tests.yml:72,:251;coverage-comment.yml:85) lint.yml:174,deploy-pages.yml:140,ci-timing.yml:53,cron-vendor.yml:151,cron-conda.yml:151andcreate-release.yml:224
Ruling (the owner, in chat): the gates and the full suite always run on the latest supported version, so 3.15 now.
Fix. Move every single-interpreter job whose version means "the newest" to 3.15. Add a test that fails whenever one of them lags the newest supported version, so the next bump cannot leave one behind. A pin kept older for a measured reason is listed in the PR, with that reason. #1660 later derives this pointer from its tier file.
None of these job names is a required check: ruleset 23497679 requires only Required checks passed and Compat Python 3.11 to 3.15.
Activity
JarryShaw commentedon Oct 13, 2026
Folded into #1660, at the owner's direction (in chat). The "latest version" pin belongs in the version-matrix work, so it is auditable in one place and can be updated automatically, rather than as 3.15 hand-edits now.
The worker already running on this issue is finishing its inventory: which single-interpreter jobs mean "the newest", and whether each one's dependencies install on 3.15. Its findings go to #1660 rather than into a separate PR. Closing as not planned here; #1660 carries the scope.
ci(python): declare the version tiers and the latest version in one f…
ci(python): declare the version tiers and the latest version in one f…
ci(python): declare the version tiers and the latest version in one f…