Repository navigation
Commit 0830fd1
authored
Build the full wheel matrix weekly, not only at release (msgspec#1174)
`build-wheels.yml` skips every musllinux wheel unless `build-all` is
true, and `ci.yml` only passes `build-all` on release. So no musllinux
wheel, on any architecture, is built outside a release, and the first
run that can show a musllinux breakage is the one meant to publish.
msgspec#1134 hit exactly that when `cp310-musllinux_riscv64` failed on the
0.22.0 release build, and msgspec#1146 could not be exercised by its own CI for
the same reason.
**Change.** `ci.yml` gains a weekly `schedule` trigger (Monday 04:17
UTC) and passes `build-all` on `schedule` as well as on `release`, so
the complete matrix, musllinux and riscv64 included, runs on a timer
between releases. Pull request and push runs are unchanged, and so is
the `build-riscv64` label gate. Five lines, no new jobs.
**What proves it.** A workflow cannot run locally; the file parses as
YAML. The first scheduled run showing the musllinux and riscv64 legs
outside a release is the proof. If PR-time coverage is wanted as well, a
single `cp312-musllinux_x86_64` smoke build gated on changes to the
wheel workflow, `setup.py`, `pyproject.toml` or `src/` is a small
follow-up; I left it out of this change so the schedule can land on its
own.
One question for the reviewer: is weekly the right cadence for the
project's CI budget, or would you rather tie the full build to a
pre-release tag?
Closes msgspec#11501 parent 924f477 commit 0830fd1
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
38 | 42 | | |
39 | 43 | | |
40 | 44 | | |
| |||
201 | 205 | | |
202 | 206 | | |
203 | 207 | | |
204 | | - | |
| 208 | + | |
205 | 209 | | |
206 | 210 | | |
207 | 211 | | |
| |||
0 commit comments