Skip to content

ci: migrate 14 workflows to needs.setup.outputs.matrix (batch 5/8) - #4927

Open
luhenry wants to merge 11 commits into
mainfrom
fix/matrix-batch-5
Open

luhenry wants to merge 11 commits into
mainfrom
fix/matrix-batch-5

Conversation

@luhenry

@luhenry luhenry commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Part of the repo-wide move off hardcoded python:/libc: build matrices and
onto needs.setup.outputs.matrix, which _setup.yml already derives
directly from each pending version's docs/packages/<pkg>.yaml files:
entries. This is batch 5/8, covering 14 packages.

Converted (11)

Each build_wheels job's strategy.matrix becomes
include: ${{ fromJSON(needs.setup.outputs.matrix) }}, and every remaining
matrix.libc reference in that job is renamed to matrix.platform (job
name:, CIBW_BUILD/only:, upload-artifact name:, and any inline
expression using it).

  • ncompress — mismatch found: the hardcoded [cp312, cp314t] never built
    the cp310/cp311 targets the pending 1.0.2 release declares, and built
    cp314t, which the YAML doesn't declare at all (the single abi3 build is at
    cp312-abi3). Fixed as a side effect.
  • ngt — clean match (cp312-cp314t, manylinux-only); no libc dimension
    existed, nothing to rename. No version is currently pending.
  • openstep-plist — mismatch: missing cp310/cp311 for the pending 0.5.2
    release. Fixed as a side effect.
  • pcapy-ng — mismatch: missing cp310/cp311 for the pending 2.1.0
    release. Its cp314t exclusion (comment: no free-threaded wheel upstream)
    needed no python-exclude, since the YAML never declares a 3.14t target
    for this package at all.
  • pemja — mismatch, and the most unusual one: missing cp310/cp311 for
    all three pending versions (0.5.7, 0.6.2, 0.6.3), and for 0.6.3 the old
    array targeted cp314/cp314t while the YAML actually declares cp315t.
    Dropped the now-redundant per-version exclude: block too (0.5.7's gap is
    already implied by its YAML files:).
  • polyscope — mismatch: missing cp310/cp311 for the pending 2.6.1
    release.
  • posix-ipc — mismatch in both directions: missing cp310/cp311, and
    the old array also targeted cp314/cp314t, which the YAML does not
    declare for 1.3.2 at all.
  • potpourri3d — mismatch: missing cp310/cp311 for the pending 1.4.0
    release. Also renamed matrix.libc inside the CIBW_BEFORE_ALL_LINUX
    ternary expression.
  • private-attribute-cpp — the largest mismatch in this batch: all 13
    pending versions (2.1.17 through 2.2.7) declare cp310, cp311, cp313t,
    cp315 and cp315t targets that the hardcoded [cp312-cp314t] array never
    built.
  • py-radix — mismatch: missing cp310/cp311 for the pending 1.1.0
    release.
  • pycapnp — mismatch: missing cp310/cp311 for the pending 2.2.4
    release.

(The cp310/cp311 gap above is the same shape in every case: these two
interpreters became available after each workflow's matrix was authored and
the hardcoded arrays were never updated to match.)

Left unconverted (3) — flagged for manual follow-up

  • onnxruntime — has a genuine per-version safety exclusion that this
    structural change can't carry over mechanically: cp314t is excluded only
    for 1.30.0/1.31.0/1.31.1 (documented heap-corruption SIGABRT), not for
    1.29.0. python-exclude on the setup: job is global to the whole run, not
    per-version, and GitHub Actions' exclude: is applied before include: is
    merged in, so it can't filter combinations that come purely from
    include:. Naively converting would either silently re-enable the crashing
    cp314t build for the three bad versions, or (with a blanket
    python-exclude: cp314t) wrongly drop cp314t from 1.29.0, where it
    builds and tests fine. Separately, the YAML also declares cp311 and
    cp313t targets for every version that the hardcoded array never
    attempted, with no comment explaining why — also needs a maintainer call.
    Left as-is rather than guessing.
  • openturns — non-standard shape: build_wheels' strategy.matrix has
    only version:, no python:/libc: array to replace — it builds a single
    hardcoded cp310-abi3-manylinux wheel via job-level PYDIR/WHEEL_TAG env
    vars rather than a cibuildwheel matrix. test_wheels' python: [cp310, cp312, cp313, cp314] matrix is a separate ABI-compatibility test sweep
    across every interpreter, not a per-interpreter build axis, so it isn't the
    duplication this migration targets either. Left both unconverted.
  • pandas — flagged per the task's own caution, high-impact package.
    Non-standard: the old matrix has no libc: dimension at all, and only: ${{ matrix.python }}-manylinux_riscv64 hardcodes the literal string
    manylinux_riscv64 rather than referencing a matrix field — pandas
    currently builds manylinux only. But docs/packages/pandas.yaml does
    declare musllinux targets for every pending version, so a mechanical
    conversion would silently start building musllinux wheels for pandas for
    the first time. The workflow's env: block also only defines
    MANYLINUX_RISCV64_IMAGE, with no MUSLLINUX_RISCV64_IMAGE for
    CIBW_MUSLLINUX_RISCV64_IMAGE to reference — building musllinux as-is
    would likely fail outright. Given pandas's blast radius (many dependents),
    this needs a deliberate, tested change rather than a mechanical one. Left
    unconverted.

Verification

For each converted package, ran uv run --quiet ci_scripts/pending_versions.py --python-matrix --python-exclude cp39 <pkg> and compared the
(python, platform) pairs per pending version against what the old
hardcoded python:/libc: lists would have produced, as described above.
Also confirmed no .github/workflows/*.yml file in this branch has a
lingering matrix.libc reference, and that all 14 touched files still parse
as valid YAML.

No docs/packages/*.yaml, .queue.yml, or skills/ changes in this branch.

Drops the hardcoded python/libc matrix in favor of the matrix _setup.yml
already derives from docs/packages/ncompress.yaml's files: entries, and
renames matrix.libc to matrix.platform to match its field names.

The old hardcoded list (cp312, cp314t) was stale: it never built the
cp310/cp311 non-abi3 targets the YAML declares, and built cp314t, which
the YAML does not declare at all. The generated matrix fixes both as a
side effect.
Drops the hardcoded python matrix in favor of the matrix _setup.yml
already derives from docs/packages/ngt.yaml's files: entries. No libc
dimension existed (manylinux-only), so nothing to rename. The old
hardcoded list (cp312, cp313, cp314, cp314t) matches the generated
matrix exactly for the current release; no mismatch found.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/openstep-plist.yaml's
files: entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was stale: it never built the
cp310/cp311 targets the pending 0.5.2 release declares. Fixed as a
side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/pcapy-ng.yaml's files:
entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314) was stale: it never built the
cp310/cp311 targets the pending 2.1.0 release declares. Its cp314t
exclusion needed no equivalent python-exclude, since the YAML never
declares a 3.14t target for pcapy-ng at all.
Drops the hardcoded python matrix and its version-keyed exclude list
in favor of the matrix _setup.yml already derives from
docs/packages/pemja.yaml's files: entries. No libc dimension existed.

The old hardcoded list (cp312-cp314t, minus cp313/cp314/cp314t for
0.5.7) was stale for every pending version: it never built the
cp310/cp311 targets any of 0.5.7/0.6.2/0.6.3 declare, and for 0.6.3 it
targeted cp314/cp314t instead of the cp315t the YAML actually declares.
Fixed as a side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/polyscope.yaml's files:
entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was stale: it never built the
cp310/cp311 targets the pending 2.6.1 release declares. Fixed as a
side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/posix-ipc.yaml's files:
entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was stale in both directions for
the pending 1.3.2 release: it never built the cp310/cp311 targets the
YAML declares, and attempted cp314/cp314t targets the YAML does not
declare at all. Fixed as a side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/potpourri3d.yaml's
files: entries, and renames matrix.libc to matrix.platform, including
in the CIBW_BEFORE_ALL_LINUX conditional.

The old hardcoded list (cp312-cp314t) was stale: it never built the
cp310/cp311 targets the pending 1.4.0 release declares. Fixed as a
side effect of the structural change.
…trix

Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/private-attribute-cpp.yaml's
files: entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was badly stale: all 13 pending
versions (2.1.17 through 2.2.7) declare cp310, cp311, cp313t, cp315
and cp315t targets that the hardcoded matrix never built. Fixed as a
side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/py-radix.yaml's files:
entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was stale: it never built the
cp310/cp311 targets the pending 1.1.0 release declares. Fixed as a
side effect of the structural change.
Drops the hardcoded python/libc matrix in favor of the matrix
_setup.yml already derives from docs/packages/pycapnp.yaml's files:
entries, and renames matrix.libc to matrix.platform.

The old hardcoded list (cp312-cp314t) was stale: it never built the
cp310/cp311 targets the pending 2.2.4 release declares. Fixed as a
side effect of the structural change.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant