Repository navigation
Build the full wheel matrix weekly, not only at release - #1174
Merged
Siyet merged 1 commit intoSep 11, 2026
Merged
Conversation
Problem: build-wheels.yml skips every musllinux wheel unless build-all is true, and ci.yml sets build-all only on release. No musllinux wheel, on any architecture, was built outside a release, so the first run that could show a musllinux breakage was 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. What proves it: the first scheduled run showing the musllinux and riscv64 legs outside a release. A workflow cannot be run locally; the file was checked with a YAML parse.
Siyet
added this pull request to the merge queue
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
build-wheels.ymlskips every musllinux wheel unlessbuild-allis true, andci.ymlonly passesbuild-allon 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. #1134 hit exactly that whencp310-musllinux_riscv64failed on the 0.22.0 release build, and #1146 could not be exercised by its own CI for the same reason.Change.
ci.ymlgains a weeklyscheduletrigger (Monday 04:17 UTC) and passesbuild-allonscheduleas well as onrelease, so the complete matrix, musllinux and riscv64 included, runs on a timer between releases. Pull request and push runs are unchanged, and so is thebuild-riscv64label 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_64smoke build gated on changes to the wheel workflow,setup.py,pyproject.tomlorsrc/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 #1150