Repository navigation
ci(python): pypcap-parity has no leg left once 3.11 reaches end of life (after #1746) #1747
Description
Describe the bug
After #1746 (#1738), the pypcap-parity matrix holds supported legs only, and its KTLO legs live in pypcap-parity-ktlo. Once 3.11 reaches end-of-life it becomes KTLO, and pypcap-parity is left with no leg. Running update_python_versions' three_eleven_ends scenario on the #1746 branch produces "pypcap-parity (zero)". required-checks still needs: pypcap-parity, so the updater's own PR would probably go red. How GitHub treats an empty matrix has not been confirmed from docs.github.com.
Expected behavior
When a tier goes empty, CI stays green and the updater says so. One fix is to retire the job, or move parity to another supported version. Another is to have required-checks accept skipped for an empty matrix. The same exposure applies to the KTLO jobs and to experimental.yml if their tiers empty out.
Additional context
The updater emits no manual note for this case today.
Activity
JarryShaw commentedon Oct 14, 2026
I think the updater just ask me to retire/remove the step/job?
JarryShaw commentedon Oct 14, 2026
Recorded: the updater does not retire anything itself. When a job's matrix would go empty, as
pypcap-paritywill once 3.11 reaches end of life, its proposal flags it as a manual step that names the job and asks you to retire or remove it. It does not quietly write a zero-leg matrix. That editsutil/update_python_versions.py, which #1746 also changes, so this starts once #1746 merges.JarryShaw commentedon Oct 14, 2026
#1746 has merged, so this is unblocked. A worker is on it.
ci(python): the version updater flags a job its update would empty (#…