Repository navigation
ci: upgrade cibuildwheel 4.1.0 -> 4.3.1 - #1
Open
pylaterreur wants to merge 1 commit into
Open
pylaterreur wants to merge 1 commit into
pylaterreur wants to merge 1 commit into
Conversation
cibuildwheel 4.1.0 builds the macOS and Windows CPython 3.15 wheels against its pinned 3.15.0b2, and cibuildwheel advises against distributing wheels built before 3.15.0rc1 because the ABI could still change. 4.2.0 moved to 3.15.0rc1 and 4.3.1 to the final 3.15.0. Linux is unaffected: the jobs use the latest manylinux and musllinux images, which already have 3.15.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GwUvhmzgfkiZ6vo4uGyesN
Author
|
I verified this on my fork. I ran this commit with the wheel matrix cut down to the 14 cp315/cp315t jobs, and all 14 pass. The macOS and Windows wheels are now built and tested against the final 3.15.0:
Each job's tests passed: 248 passed and 44 skipped for the C backend, 224 passed and 68 skipped for CFFI. |
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.
For indygreg#357: with cibuildwheel 4.1.0, the macOS and Windows
cp315/cp315twheels are built against CPython 3.15.0b2, the prerelease that 4.1.0 pins. From your fork's run of this branch:Python 3.15.0b2 (v3.15.0b2:94a64bbc6ce, Jun 2 2026, 11:57:29) [Clang 21.0.0 (clang-2100.1.1.101)]Python 3.15.0b2 (tags/v3.15.0b2:94a64bb, Jun 2 2026, 15:56:22) [MSC v.1951 64 bit (AMD64)]cibuildwheel advises against distributing wheels built against a 3.15 beta, because the ABI could still change before RC1. 4.2.0 moved to 3.15.0rc1, and 4.3.1, the latest release, to the final 3.15.0. The Linux jobs aren't affected: they use the
:latestmanylinux and musllinux images, which already have 3.15.0.This is what each version pins, per
cibuildwheel.platforms.macos/windows(I checked it locally):cp315/cp315tmacOS (x86_64, arm64)python-3.15.0b2-macos11.pkgpython-3.15.0-macos11.pkgcp315/cp315tWindows (win32, win_amd64, win_arm64)3.15.0-b23.15.0The releases from 4.1.1 to 4.3.1 don't change anything this config relies on. With this
pyproject.tomland the workflow'sCIBW_*settings,--print-build-identifiersselects the same builds under both versions. The image digests that 4.1.1 pins don't apply here, because the workflow sets its own:latestimages. A run on my fork, limited to the cp315/cp315t jobs, confirms it (see the comment below).Prepared with the help of Claude Code.
🤖 Generated with Claude Code