[WIP] newest dense matmul bindings and change build backend to scikit-build #31
Transurgeonbuild-and-publish.yml
on: pull_request
Annotations
19 errors and 12 warnings
|
build_wheels (windows-2022, 3.11)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (windows-2022, 3.11)
The operation was canceled.
|
|
build_wheels (macos-14, 3.14)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (macos-14, 3.14)
The operation was canceled.
|
|
build_wheels (windows-2022, 3.13)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (windows-2022, 3.13)
The operation was canceled.
|
|
build_wheels (windows-2022, 3.12)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (windows-2022, 3.12)
The operation was canceled.
|
|
build_wheels (windows-2022, 3.14)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (windows-2022, 3.14)
The operation was canceled.
|
|
build_wheels (ubuntu-22.04, 3.12)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (ubuntu-22.04, 3.12)
The operation was canceled.
|
|
build_wheels (ubuntu-22.04, 3.14)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (ubuntu-22.04, 3.14)
The operation was canceled.
|
|
build_wheels (ubuntu-22.04, 3.11)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (ubuntu-22.04, 3.11)
The operation was canceled.
|
|
build_wheels (ubuntu-22.04, 3.13)
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_wheels (ubuntu-22.04, 3.13)
The operation was canceled.
|
|
Build and publish
Canceling since a higher priority waiting request for newest-dense-matmul-bindings exists
|
|
build_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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (macos-14, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (macos-14, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (macos-14, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (windows-2022, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (windows-2022, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (windows-2022, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (windows-2022, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (ubuntu-22.04, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (ubuntu-22.04, 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (ubuntu-22.04, 3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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_wheels (ubuntu-22.04, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
|
45.6 KB |
sha256:cecb071620aef505e5170e875541037c08a332d4131ff5c3ebee81c4e963a5aa
|
|
|
wheels-macos-14-3.11
|
234 KB |
sha256:38cb77e9c7f87a664036eb4625e194e0f3c5b8a1c7210916b526cdb79c84e7d6
|
|
|
wheels-macos-14-3.12
|
234 KB |
sha256:7d550c8b3a29965d05d2967044b0c1683238ae50c548e7e0a5747d84c0cdff32
|
|
|
wheels-macos-14-3.13
|
234 KB |
sha256:0217c382e49783f634d1fa0ec8976be8152f04ecdbfb47235b10368d634e8c77
|
|