ci(publish): make free-threaded wheel builds non-blocking; fail-fast: false#211
Merged
Conversation
… false cp314t free-threaded cross-builds flake under QEMU emulation, and with the all-arches release gate a single flake blocks the entire PyPI upload. Mark the free-threaded build steps continue-on-error, and set fail-fast: false so a stray emulated-build flake isolates to one matrix leg instead of cancelling its siblings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Harden the release publish workflow against flaky QEMU-emulated cross-builds (same fix just applied to seqpro):
continue-on-error: trueon the 4Build free-threaded wheels(cp314t) steps — a free-threaded flake no longer fails the job, so the stable wheels still upload.fail-fast: falseon the build matrices — a stray emulated-build flake isolates to one matrix leg instead of cancelling its siblings, so a re-run only needs to retry the one flaked leg.Without this, a single flaky free-threaded/emulated build blocks the entire PyPI upload (the
releasejob needs every build job).Test plan
🤖 Generated with Claude Code