Skip to content

releases

releases #52

Triggered via release March 17, 2026 15:52
@andthattooandthattoo
published 5cfb9fb
Status Failure
Total duration 8m 14s
Artifacts 6

releases.yml

on: release
Matrix: build-cuda
Matrix: build
build-rocm
24s
build-rocm
release
0s
release
update_homebrew
0s
update_homebrew
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
build-cuda (ubuntu-latest, linux, amd64-cuda, x86_64-unknown-linux-gnu, 12.8.0)
Error: Version not available: 12.8.0
build-cuda (windows-latest, windows, amd64-cuda, x86_64-pc-windows-msvc, 12.8.0, .exe)
The strategy configuration was canceled because "build-cuda.ubuntu-latest_linux_amd64" failed
build-rocm
Process completed with exit code 100.
build-cuda (ubuntu-latest, linux, amd64-cuda, x86_64-unknown-linux-gnu, 12.8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, Jimver/cuda-toolkit@v0.2.19. 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-rocm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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 (macos-latest, macOS, arm64, aarch64-apple-darwin, build, --features metal)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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 (ubuntu-latest, linux, amd64-noavx, x86_64-unknown-linux-gnu, build, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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 (ubuntu-latest, linux, amd64, x86_64-unknown-linux-gnu, build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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 (macos-latest, macOS, amd64, x86_64-apple-darwin, build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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 (windows-latest, windows, amd64, x86_64-pc-windows-msvc, build, .exe)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/

Artifacts

Produced during runtime
Name Size Digest
dria-node-linux-amd64
5.68 MB
sha256:552df1cb29580497cf595cc54863db6ecff466cb13a4f12f687b966d8554a2f5
dria-node-linux-amd64-noavx
5.68 MB
sha256:f9fb65d7b3cdc65ddfe9503c87f5bc0d4722f5854bd68676f8c952c7681fb21c
dria-node-linux-arm64
5.37 MB
sha256:9461d1ee0dfb50f6d286896a74b9f3e17a2979a08be9e94f53cb0867f139c265
dria-node-macOS-amd64
5.5 MB
sha256:08ea3d99e22be27e243f226e21cc3aaa668749c2131feb6f2675c30497cd0c11
dria-node-macOS-arm64
5.28 MB
sha256:f37aae3a6d4923002e1fb803a3b61396c641bfd19579d4b8ad505e3cfb1e1c4e
dria-node-windows-amd64
5.32 MB
sha256:d1a24af17157a6c059dc11854e53756d2e9dadc9b99be8ac7b7e004be362edaf