Merge: Hardening Memory Access & Comparison Logic #134
ashvardanianrelease.yml
on: push
Update Version
12s
Matrix: build_wheels_stringzilla_linux
Matrix: build_wheels_stringzilla_macos
Matrix: build_wheels_stringzilla_windows
Matrix: build_wheels_stringzillas_cpus_linux
Matrix: build_wheels_stringzillas_cpus_macos
Matrix: build_wheels_stringzillas_cpus_windows
Matrix: build_wheels_stringzillas_cuda_linux
Matrix: create_linux_deb_package
Matrix: create_macos_library
Matrix: create_windows_dll_library
Publish JavaScript
11s
Linux CI
3s
macOS CI
3s
Windows CI
4s
Publish StringZilla to PyPI
3m 37s
Publish StringZillas-CPUs to PyPI
31s
Publish StringZillas-CUDA to PyPI
18s
Annotations
37 errors, 78 warnings, and 42 notices
|
Build StringZillas-CPUs 313 for macOS
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 313 for macOS
Command ['arch', '-x86_64', '/bin/sh', '-c', 'python /Users/runner/work/StringZilla/StringZilla/build_backend.py run-tests /Users/runner/work/StringZilla/StringZilla'] failed with code 1.
|
|
Build StringZillas-CPUs 310 for macOS
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 310 for macOS
Command ['/bin/sh', '-c', 'python /Users/runner/work/StringZilla/StringZilla/build_backend.py run-tests /Users/runner/work/StringZilla/StringZilla'] failed with code 1.
|
|
Build StringZillas-CUDA 313 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 313 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Build StringZillas-CPUs 311 for macOS
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 311 for macOS
Command ['/bin/sh', '-c', 'python /Users/runner/work/StringZilla/StringZilla/build_backend.py run-tests /Users/runner/work/StringZilla/StringZilla'] failed with code 1.
|
|
Build StringZillas-CPUs 39 for macOS
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 39 for macOS
Command ['/bin/sh', '-c', 'python /Users/runner/work/StringZilla/StringZilla/build_backend.py run-tests /Users/runner/work/StringZilla/StringZilla'] failed with code 1.
|
|
Build StringZillas-CPUs 312 for macOS
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 312 for macOS
Command ['/bin/sh', '-c', 'python /Users/runner/work/StringZilla/StringZilla/build_backend.py run-tests /Users/runner/work/StringZilla/StringZilla'] failed with code 1.
|
|
Build StringZillas-CUDA 311 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 311 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Build StringZillas-CUDA 312 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 312 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Build StringZillas-CUDA 310 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 310 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Publish JavaScript
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 38 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 38 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Build StringZillas-CUDA 39 for ubuntu-24.04
Process completed with exit code 1.
|
|
Build StringZillas-CUDA 39 for ubuntu-24.04
Command ['python', '-m', 'pip', 'wheel', PurePosixPath('/project'), '--wheel-dir=/tmp/cibuildwheel/built_wheel', '--no-deps'] failed with code 1.
|
|
Build StringZillas-CPUs 310 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 310 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
macOS CI
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 312 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 312 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
Build StringZillas-CPUs 311 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 311 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
Build StringZillas-CPUs 313 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 313 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
Build StringZillas-CPUs 39 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 39 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
Build StringZillas-CPUs 38 for Ubuntu
Process completed with exit code 1.
|
|
Build StringZillas-CPUs 38 for Ubuntu
Command ['sh', '-c', 'python /project/build_backend.py run-tests /project'] failed with code 1.
|
|
Linux CI
Process completed with exit code 1.
|
|
Update Version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. 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 StringZillas-CPUs Source Distribution
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 313 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.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 StringZilla 313 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 310 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.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/
|
|
Create Library for MacOS arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: xresloader/upload-to-github-release@v1. 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 StringZillas-CPUs 312 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 312 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CPUs 310 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 310 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZilla 312 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 311 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 311 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CUDA 313 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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/
|
|
Publish Rust
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: katyo/publish-crates@v2. 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 StringZilla 38 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 38 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 38 for macOS
While cibuildwheel can build CPython 3.8 universal2/arm64 wheels, we cannot test the arm64 part of them, even when running on an Apple Silicon machine. This is because we use the x86_64 installer of CPython 3.8. See the discussion in https://github.com/pypa/cibuildwheel/pull/1169 for the details. To silence this warning, set `CIBW_TEST_SKIP: "cp38-macosx_*:arm64"`.
|
|
Build StringZillas-CUDA Source Distribution
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 311 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.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 StringZilla 310 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 310 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Create Debian Package for amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: xresloader/upload-to-github-release@v1. 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 StringZillas-CPUs 39 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.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 StringZillas-CPUs 38 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 310 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 311 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 312 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 312 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CPUs 312 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.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 StringZillas-CUDA 311 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CUDA 312 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZilla Source Distribution
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CUDA 310 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZilla 39 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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/
|
|
Create Dll Library for Windows x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1, xresloader/upload-to-github-release@v1. 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 StringZilla 313 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 313 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CPUs 39 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 39 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZilla 39 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZilla 39 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Create Debian Package for arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: xresloader/upload-to-github-release@v1. 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 StringZillas-CPUs 311 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 311 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CUDA 38 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 313 for Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 313 for Windows
While arm64 wheels can be built on other platforms, they cannot be tested. An arm64 runner is required. To silence this warning, set `CIBW_TEST_SKIP: "*-win_arm64"`.
|
|
Build StringZillas-CUDA 39 for ubuntu-24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 38 for macOS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4. 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 StringZillas-CPUs 38 for macOS
While cibuildwheel can build CPython 3.8 universal2/arm64 wheels, we cannot test the arm64 part of them, even when running on an Apple Silicon machine. This is because we use the x86_64 installer of CPython 3.8. See the discussion in https://github.com/pypa/cibuildwheel/pull/1169 for the details. To silence this warning, set `CIBW_TEST_SKIP: "cp38-macosx_*:arm64"`.
|
|
Build StringZillas-CPUs 310 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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/
|
|
Publish StringZillas-CUDA to PyPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
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.
|
|
Publish StringZillas-CUDA to PyPI
Unexpected input(s) 'if-no-artifact-found', valid inputs are ['name', 'artifact-ids', 'path', 'pattern', 'merge-multiple', 'github-token', 'repository', 'run-id']
|
|
Build StringZillas-CPUs 312 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 311 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 313 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 39 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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 StringZillas-CPUs 38 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, docker/setup-qemu-action@v3. 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/
|
|
Publish StringZillas-CPUs to PyPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
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.
|
|
Publish StringZillas-CPUs to PyPI
Unexpected input(s) 'if-no-artifact-found', valid inputs are ['name', 'artifact-ids', 'path', 'pattern', 'merge-multiple', 'github-token', 'repository', 'run-id']
|
|
Build StringZilla 38 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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 StringZilla 312 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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 StringZilla 310 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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 StringZilla 39 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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 StringZilla 313 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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 StringZilla 311 for Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5.2.0, actions/upload-artifact@v4, docker/setup-qemu-action@v3. 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/
|
|
Publish StringZilla to PyPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
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.
|
|
Publish StringZilla to PyPI
Unexpected input(s) 'if-no-artifact-found', valid inputs are ['name', 'artifact-ids', 'path', 'pattern', 'merge-multiple', 'github-token', 'repository', 'run-id']
|
|
Build StringZillas-CPUs 312 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZillas-CPUs 312 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZillas-CPUs 312 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp312-win_arm64.pyd for cross-compilation
|
|
Build StringZillas-CPUs 312 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-si5xqdhx\cp312-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZillas-CPUs 310 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZillas-CPUs 310 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZillas-CPUs 310 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp310-win_arm64.pyd for cross-compilation
|
|
Build StringZillas-CPUs 310 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-7_wl6how\cp310-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZilla 311 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZilla 311 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZilla 311 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp311-win_arm64.pyd for cross-compilation
|
|
Build StringZilla 311 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-kxi27sxq\cp311-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZilla 38 for macOS
Setting SYSTEM_VERSION_COMPAT=0 to ensure CPython 3.8 can get correct macOS version and allow installation of wheels with MACOSX_DEPLOYMENT_TARGET >= 11.0. See https://github.com/pypa/cibuildwheel/issues/1767 for the details.
|
|
Build StringZilla 310 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZilla 310 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZilla 310 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp310-win_arm64.pyd for cross-compilation
|
|
Build StringZilla 310 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-zsdxpc8p\cp310-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZilla 312 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZilla 312 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZilla 312 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp312-win_arm64.pyd for cross-compilation
|
|
Build StringZilla 312 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-as2ict_u\cp312-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZilla 313 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZilla 313 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZilla 313 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp313-win_arm64.pyd for cross-compilation
|
|
Build StringZilla 313 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-79zkygvp\cp313-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZillas-CPUs 39 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZillas-CPUs 39 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZillas-CPUs 39 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp39-win_arm64.pyd for cross-compilation
|
|
Build StringZillas-CPUs 39 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-637cp1j3\cp39-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZilla 39 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZilla 39 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZilla 39 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp39-win_arm64.pyd for cross-compilation
|
|
Build StringZilla 39 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-tlv5ts1d\cp39-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZillas-CPUs 311 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZillas-CPUs 311 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZillas-CPUs 311 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp311-win_arm64.pyd for cross-compilation
|
|
Build StringZillas-CPUs 311 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-31k25eyh\cp311-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZillas-CPUs 313 for Windows
Setting CARGO_BUILD_TARGET=aarch64-pc-windows-msvc for cross-compilation
|
|
Build StringZillas-CPUs 313 for Windows
Setting SETUPTOOLS_USE_DISTUTILS=local as it is required for cross-compilation
|
|
Build StringZillas-CPUs 313 for Windows
Setting SETUPTOOLS_EXT_SUFFIX=.cp313-win_arm64.pyd for cross-compilation
|
|
Build StringZillas-CPUs 313 for Windows
Setting DIST_EXTRA_CONFIG=C:\Users\runneradmin\AppData\Local\Temp\cibw-run-fthv8ony\cp313-win_arm64\build\extra-setup.cfg for cross-compilation
|
|
Build StringZillas-CPUs 38 for macOS
Setting SYSTEM_VERSION_COMPAT=0 to ensure CPython 3.8 can get correct macOS version and allow installation of wheels with MACOSX_DEPLOYMENT_TARGET >= 11.0. See https://github.com/pypa/cibuildwheel/issues/1767 for the details.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
cibw-wheels-stringzilla-macos-15-0
|
397 KB |
sha256:5b8f53e548aba8147c148fd40911b331b206f617054a06a7a3e397927c1d93c6
|
|
|
cibw-wheels-stringzilla-macos-15-1
|
398 KB |
sha256:afddd4b06fa698e03b664f37dec8707c807168b6512343f2cb90a4dc5c905cfd
|
|
|
cibw-wheels-stringzilla-macos-15-2
|
398 KB |
sha256:4b68c3ce49a5e6677b521296532817c73090683f390e20f7d6cf3d04d43f8ff7
|
|
|
cibw-wheels-stringzilla-macos-15-3
|
398 KB |
sha256:da8e9c32b65d880defbb99c457f7216c0a1758232fc8b088c8867b51c715bfb3
|
|
|
cibw-wheels-stringzilla-macos-15-4
|
399 KB |
sha256:2e60d9f35b9b5be7e7d36c8f534cc9957a2a3fe1fead201363ef734322301c66
|
|
|
cibw-wheels-stringzilla-macos-15-5
|
399 KB |
sha256:74cbd70bca159453fdcb8378af3bfa970eefe09e082a4bf94349072f67d4524b
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-0
|
9.01 MB |
sha256:134c2719d0a53aff83f1246b0dafd7831dad9e2b5f7341a26543aad6271d8866
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-1
|
9.04 MB |
sha256:0e351d5c22a0e29b7cf7602b2c7b92a5a3f335b0bb3ba130c3151e5dff9894a2
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-2
|
9.04 MB |
sha256:c2cc474b337fc5cb060fab0b2808bfb46d23a14466cdec55bf3a61adb0272761
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-3
|
9.1 MB |
sha256:af931da27919b78195d5bca8fb942d720af6aea1c57b32259b7fcb2dc5d0deba
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-4
|
9.11 MB |
sha256:b169bd69d5d4ab538742f78d17e95c6f496d94e1e6e0e701499485575fc2371f
|
|
|
cibw-wheels-stringzilla-ubuntu-24.04-5
|
9.11 MB |
sha256:693d45424dc2e44d33320e0b9d5b660e039fbd55152f4246166badca19465f7b
|
|
|
cibw-wheels-stringzilla-windows-2022-0
|
270 KB |
sha256:c7f174154ee163e05876d07f8e24030b98d6e34548fcaec32249b7cc8e006e02
|
|
|
cibw-wheels-stringzilla-windows-2022-1
|
390 KB |
sha256:a2b255d4224957dcb9b1b59f404f8633a404d301c3f486ca1ae3634e3d6d66d7
|
|
|
cibw-wheels-stringzilla-windows-2022-2
|
389 KB |
sha256:f4fb4eea403b3f9e6f058bfbb248bb595cf78fcb2639135d5a61f888b8f02d21
|
|
|
cibw-wheels-stringzilla-windows-2022-3
|
389 KB |
sha256:d93c3ecb384e2c8eeecfd6f44192cecd0bbfc88bf45baec2a8abdf8eb38b019a
|
|
|
cibw-wheels-stringzilla-windows-2022-4
|
390 KB |
sha256:2d09eb5bb56287a249157c5d68bee6c793cd8cc3562bdf436fe3c9f606f1c738
|
|
|
cibw-wheels-stringzilla-windows-2022-5
|
390 KB |
sha256:435a4aa878baaf30bb2761c505aad241dcaa8e81fa1e6bbf8a01c70c8115a835
|
|
|
cibw-wheels-stringzillas-cpus-macos-15-0
|
354 KB |
sha256:b3cdc3ce90bf0af4a7c435eb4989e65b5f90eeecfd09359e3e886dbb7ed58894
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-0
|
190 KB |
sha256:efe6a0e2b6ebd854ab105fc88c4f56b45b4489874749e5c0e34d21305af03cef
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-1
|
331 KB |
sha256:abc90b49cc7a224fbc206d2d8a67b4de6b1d791bdc36b389b3d95da39fc1a385
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-2
|
331 KB |
sha256:26448e377eb2516b4b68e64eaf982cd8964f6d289420fa9b471a62b089d73e28
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-3
|
331 KB |
sha256:c236855da7c42da8ed2f2f36128f583f8d7a04b8b3c4d86d7fa9870e7d9213c2
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-4
|
331 KB |
sha256:127733e2b7547980571cda9a62529474049b85d020bb33282a7a63822ae1106a
|
|
|
cibw-wheels-stringzillas-cpus-windows-2022-5
|
332 KB |
sha256:056608630bb6468cdcb972ef87b1d10c7c941db3d0cdb073bd58fb505a502357
|
|
|
sdist-stringzilla
Expired
|
631 KB |
sha256:82e68ce4dbf89d20ab8d9969dd09c8dabaed8c08311f646c1525b1045c1e8858
|
|
|
sdist-stringzillas-cpus
Expired
|
631 KB |
sha256:103566af34f2d0dc2357e3896b57d878da5183929db4d143c6c47f86852ed91e
|
|
|
sdist-stringzillas-cuda
Expired
|
631 KB |
sha256:d413f2af86d9e383903a8aec7ab25b0cd38844c3ba6164227881490c17fa0d52
|
|