ci: smoke-test musl wheels in Alpine, then publish them#150
Merged
rahlk merged 1 commit intoJun 8, 2026
Conversation
The musl wheels build cleanly now but couldn't be validated: a musllinux wheel can't be pip-installed on the glibc manylinux build host, and the build runs inside a container so docker-in-docker isn't available. Add a stage-then-promote flow: - build-wheels uploads musl wheels under a 'musl-staging-*' artifact and skips the in-job smoke (it physically can't run on glibc). - A new 'smoke-musl' job runs per-arch on native host runners, installs and exercises each wheel inside a python:3.12-alpine (musl) container via docker, and only on success promotes it to the publishable 'wheel-*' name. So an unverified musl wheel never reaches PyPI. - github-release / publish-pypi / publish-testpypi now pull 'wheel-*' (+ sdist) only — never the staging artifacts — and wait for smoke-musl via needs, but are gated solely on the essential build jobs (always() + result checks) so the experimental musl leg can never block release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
68d7d8e
into
146-package-codeanalyzer-java-as-a-pypi-distribution-with-pypi-releaseyml
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
1 participant
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.
Completes musl support for the v2.3.7 PyPI release. Builds were already fixed (#148 download, #149 static-PIE link); musl wheels now build but weren't validated or published.
Problem
A
musllinuxwheel can't bepip installed on the glibc manylinux build host, and that job runs inside a container (no docker-in-docker), so the wheel can't be tested where it's built.Stage-then-promote
musl-staging-*artifact and skip the in-job smoke (can't run on glibc).python:3.12-alpine(musl) container via docker (codajv --versionand a level-1-sanalysis). Only on success does it promote the wheel to the publishablewheel-*name — so an unverified musl wheel never reaches PyPI.wheel-*(+ sdist) only, never staging; theyneeds: smoke-muslfor ordering but gate solely on the essential build jobs (always()+ result checks), so the experimental musl leg can never block the glibc/macOS release.After merge I'll re-tag
v2.3.7once more to publish the two musl wheels (PyPI publish isskip-existing, so the already-live wheels/sdist are untouched).🤖 Generated with Claude Code