Skip to content

Add CFLAGS, LDFlAGS and PKG_CONFIG for building lxml #572

Add CFLAGS, LDFlAGS and PKG_CONFIG for building lxml

Add CFLAGS, LDFlAGS and PKG_CONFIG for building lxml #572

Triggered via push April 27, 2026 16:06
Status Cancelled
Total duration 9m 18s
Artifacts 11

wheels.yml

on: push
Matrix: cache_libs / cache_libs
Generate wheels matrix
12s
Generate wheels matrix
Matrix: build_wheels
Fit to window
Zoom out
Zoom in

Annotations

57 errors and 26 warnings
Build for cp311-manylinux_riscv64
Process completed with exit code 1.
Build for cp311-manylinux_riscv64
cibuildwheel: Command ['sh', '-c', 'yum install -y perl-core'] failed with code 1.
Build for cp39-manylinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-manylinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-manylinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-manylinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-manylinux_riscv64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-manylinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-manylinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-manylinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-musllinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-manylinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-manylinux_riscv64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-manylinux_riscv64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-musllinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-musllinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-manylinux_riscv64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-win_amd64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-win_amd64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp311-win_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-win_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-macosx_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-win_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-win_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-win_arm64
The operation was canceled.
Build for cp310-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp310-musllinux_aarch64
The operation was canceled.
Build for cp312-manylinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-manylinux_aarch64
The operation was canceled.
Build for cp314-win_amd64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-musllinux_aarch64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-musllinux_aarch64
The operation was canceled.
Build for cp312-macosx_arm64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-macosx_arm64
The operation was canceled.
Build for cp313-manylinux_riscv64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp313-manylinux_riscv64
The operation was canceled.
Build for cp312-manylinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp312-manylinux_x86_64
The operation was canceled.
Build for cp314-musllinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp314-musllinux_x86_64
The operation was canceled.
Build for cp39-musllinux_x86_64
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
Build for cp39-musllinux_x86_64
The operation was canceled.
Wheel build
Canceling since a higher priority waiting request for Wheel build-refs/heads/fix-linuxbrew-workflow exists
cache_libs / cache_libs (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cache_libs / cache_libs (ubuntu-22.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cache_libs / cache_libs (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cache_libs / cache_libs (windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
cache_libs / cache_libs (windows-11-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp311-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp313-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp39-win_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp311-manylinux_riscv64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp314-win_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp311-manylinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp310-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp314-manylinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp313-musllinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp313-musllinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp310-win_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp310-musllinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp312-manylinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp314-win_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, actions/upload-artifact@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp39-musllinux_aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp312-macosx_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp313-manylinux_riscv64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp312-manylinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp314-musllinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build for cp39-musllinux_x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4.3.0, docker/setup-qemu-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
sdist
70.5 KB
sha256:0a8e045c35161018b6cbaeb57034458b58a4177348b596249773808a627c4c1c
xmlsec-wheel-cp310-win_amd64
2.53 MB
sha256:3c03b24257fd3c492c1ba8ccf2661278175c3491976b954eb4951fba4c9db17d
xmlsec-wheel-cp311-manylinux_x86_64
3.95 MB
sha256:950395b04f23bb72026f4d178c3e8ceef1f4ca80ea9c71824e15425bda7348ea
xmlsec-wheel-cp311-win_amd64
2.53 MB
sha256:9a461ed11ca7199352dffcccd099aef596b3c635d660ce11a16d5202b5166709
xmlsec-wheel-cp313-musllinux_aarch64
4.24 MB
sha256:d813181ec149dce97ec48ea3234ac591de9950ffbde1285fef7b537a325fd9bb
xmlsec-wheel-cp313-musllinux_x86_64
4 MB
sha256:44290388b97c96269fd2f1368cd4c83eed50376d6c1285c593e819e5b3551307
xmlsec-wheel-cp313-win_amd64
2.53 MB
sha256:092ba089b49658d4a5a044064596171110d67bf4631befd324e393492e254a6e
xmlsec-wheel-cp314-manylinux_aarch64
4.2 MB
sha256:0a58314a5cf2ffe2b477cf1772e6bb94798a7111118cec2f86e014bacca9f1d0
xmlsec-wheel-cp314-win_amd64
2.6 MB
sha256:2bf9e0429d8f160816983d5125332586dc92d4ab4601581eeec754a01f35e89e
xmlsec-wheel-cp314-win_arm64
2.4 MB
sha256:7718c6d0662fee7c33b64d274f82d088a8f22fcb6892b4051dd58c566bc4ced9
xmlsec-wheel-cp39-win_arm64
2.33 MB
sha256:66beb937978e7a94cc2f095b1cee5d05e881df84e1a06c0717483b57a0eb37e7