Skip to content
Python wheels

Getting ready for release 4.12.0 #2407

Sign in to view logs

Getting ready for release 4.12.0

Getting ready for release 4.12.0 #2407

Triggered via push September 1, 2026 09:34
@FrancescAltedFrancescAlted
pushed 11428b4
v4.12.0
Status Success
Total duration 21m 10s
Artifacts 6

cibuildwheels.yml

on: push
Matrix: build_wheels
Matrix: build_wheels_wasm
Matrix: test_abi3_matrix
upload_pypi
40s
upload_pypi
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Build wheels on ubuntu-24.04-arm for aarch64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1.13.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build wheels on ubuntu-latest for x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1.13.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build wheels on windows-latest for x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1.13.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build wheels on macos-latest for x86_64
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: ilammy/msvc-dev-cmd@v1.13.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build WASM/Pyodide wheels for 3.14
cibuildwheel: Invalid test_skip selector: 'cp315*-macosx_x86_64'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
Build WASM/Pyodide wheels for 3.13
cibuildwheel: Invalid test_skip selector: 'cp315*-macosx_x86_64'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Artifacts

Produced during runtime
Name Size Digest
linux-aarch64
17.4 MB
sha256:dfe6e7260d6ddd939f51ed0f218defda632ed3ef35210229c2ddc2c4a9c6b746
linux-x86_64
25.3 MB
sha256:620fa5db9e652599dafb369f70e5b35666183c4b07e16d3c590eb0af4f5dae68
macos-universal2
30.3 MB
sha256:b4f29c2d85ac285860d924b00014c8b672870a26dfcf20c0106357eed2faad66
wasm-pyodide-cp313
2.43 MB
sha256:fb2c3836f5adb7251acfe36a6ba5e62606b938dfb195af0410a5ec4a9819b594
wasm-pyodide-cp314
2.43 MB
sha256:790ebb9f928fcbc3361110412ad1e7107f4270523abc72121a7b78266b821ed9
windows-x86_64
13.5 MB
sha256:da86cf2a7a375eed24479996fbb0391c73052343abc57d134e86c55c12dcf6a4