ci: drive build versions from docs/packages/<pkg>.yaml

[luhenry]

docs/packages/<pkg>.yaml becomes the source of truth for what a workflow builds. A - version: entry without tag:/files: is pending; _setup.yml turns the pending set into a matrix.version every job iterates over, and _publish-wheel.yml fills the entry in through the docs PR. Adding a package is two files (build-<pkg>.yml + docs/packages/<pkg>.yaml); upgrading one is a single - version: line.

Triggers

• pull_request (to main) on the workflow and its YAML: builds every pending version, dry-runs the publish.
• push to main: builds and publishes every pending version — replaces the manual post-merge dispatch. Merging the docs PR pushes an all-released YAML, so that run has an empty matrix and skips every job (green).
• workflow_dispatch takes a version glob (2.5.*), released or not, for force-rebuilds.

Infra

• _setup.yml: package (required) + version (glob) inputs; runs the new ci_scripts/pending_versions.py via uv run, outputs versions as JSON. The script also lints the YAML (tag/files pairing, duplicates).
• update_doc.py: fills the declared entry in place (byte-for-byte otherwise); fails when the wheel's version is not declared (setuptools_scm dev versions no longer get documented) or the YAML is missing; still registers first-time packages in packages.txt.
• generate_packages_doc.py: pending versions are skipped by the docs and the Simple API instead of raising.
• check_versions.py: upgrade PRs append - version: lines and nothing else — no workflow bump, no Trigger: lines, no dispatch. pr-trigger.yml is deleted.
• pr-checks.yml: lints changed package YAMLs and requires one for every changed build workflow.

Workflows (707 build-*.yml, 3 test-*.yml)
Mechanically rewritten: ${{ inputs.version || '<lit>' }} → ${{ matrix.version }}, workflow-level <PKG>_VERSION env moved to job level, if: needs.setup.outputs.versions != '[]' + version: matrix vector on every job (GHA rejects an empty matrix). Hand-finished:

• sdist→bdist workflows (45): job outputs are not per matrix leg, so the sdist artifact is named <pkg>-<version>-sdist and consumers resolve it with a sdist_path step.
• tag ≠ wheel version: 13 v-prefixed defaults move the v into ref: (their patch dirs renamed to the bare version); rtoml/dprint-py/point-cloud-utils/fabio/torch derive the tag from the version in a step.
• build-mlx.yml/build-polars-runtime.yml build two packages; they pass the primary one and the sibling YAML must be kept in lockstep (commented).
• torch/s5cmd keep a genuinely version-dependent job output; commented as one-version-at-a-time.

Verified on this branch

• Every pull_request run: setup only, build/publish skipped, green.
• gh workflow run build-ada-url.yml -f version='4.0.*' and build-cffi.yml -f version=2.1.0: matrix expands, wheels build, publish dry-run shows update_doc.py replacing the tag of the already-released entry.
• pending_versions.py, update_doc.py (pending / released / undeclared / mid-file entry) and generate_packages_doc.py exercised locally; check_versions.py --self-test passes; actionlint reports nothing new versus main.

Known limitation: a second push touching a package's YAML before its docs PR lands rebuilds the still-pending version and creates a second release; update_doc.py keeps the latest tag.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-16 10:10 UTC