Skip to content

Release

Release #144

Triggered via schedule June 4, 2026 19:55
Status Success
Total duration 51m 7s
Artifacts 25

release.yml

on: schedule
Matrix: windows-cpu
Matrix: ubuntu-22-cuda-arm64
Matrix: ubuntu-22-cuda
Matrix: ubuntu-22-rocm
Matrix: windows-rocm
ubuntu-22-openvino
3m 8s
ubuntu-22-openvino
Matrix: windows-cuda
Fit to window
Zoom out
Zoom in

Annotations

22 warnings and 1 notice
windows-rocm (7.13.0, gfx906;gfx908;gfx90a;gfx942;gfx950;gfx1010;gfx1011;gfx1012;gfx1030;gfx1031;...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_75)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_75)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AdshagAAAACgpidPBzl6Q7O/YUC2a6I6Q0hHRURHRTE5MDgARWRnZQ==
windows-cuda (sm_75)
Failed to restore: Cache service responded with 400
windows-cuda (sm_120)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_120)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RNshagAAAAAkbaiBFm4GT72S5WK5TuwDTEFYRURHRTE1MTgARWRnZQ==
windows-cuda (sm_120)
Failed to restore: Cache service responded with 400
windows-cuda (sm_89)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_89)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>05tohagAAAACPYdbZT00yT6UCxIVF36z4UEhMMzBFREdFMDQxOQBFZGdl
windows-cuda (sm_89)
Failed to restore: Cache service responded with 400
windows-cuda (sm_100)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_100)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kdshagAAAAC55NPGsDRdRbR+ejOerGSvUEhMMzBFREdFMDQyMgBFZGdl
windows-cuda (sm_100)
Failed to restore: Cache service responded with 400
windows-cuda (sm_90)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_90)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0VNwhagAAAACtZjDVoG2LTrq8Wo+Of3p4UEhYMzFFREdFMDYwOABFZGdl
windows-cuda (sm_90)
Failed to restore: Cache service responded with 400
windows-cuda (sm_86)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_86)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0g9whagAAAAAxdsk5WYOmSpp7uwZf6jqLUEhYMzFFREdFMDIxNABFZGdl
windows-cuda (sm_86)
Failed to restore: Cache service responded with 400
windows-cuda (sm_80)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Jimver/cuda-toolkit@v0.2.21. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
windows-cuda (sm_80)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dtwhagAAAABtCBb46E/xSIj3rXIpgqIRUEhYMzFFREdFMDIxMABFZGdl
windows-cuda (sm_80)
Failed to restore: Cache service responded with 400
windows-cpu (x64)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
llama-bin-ubuntu-openvino-2026.0-x64.tar.gz
108 MB
sha256:534040ae163b65ea58b56d85add76c3eace0fa99f49e8ac358bf1c7fe584984a
llama-bin-ubuntu-rocm-7.13-x64.tar.gz
212 MB
sha256:f68142c511aafb0eaa83273198071b819d350aee752bb943bb1d054f2df8fa7a
llama-bin-win-cpu-x64.zip
16.1 MB
sha256:3c88f41c1856332ea39eefd699bb9ba528f689013125f42b2b3ebeb779f641e3
llama-bin-win-rocm-7.13-x64.zip
210 MB
sha256:3191c9bd21418b41528a996b49fc0cf21b57fcad1e1bc071355a25b586d4a472
llama-ubuntu-cuda-sm_100-arm64.tar.xz
564 MB
sha256:1f076435e2d0aa2b295f78b558d1b543b24a205f6e55ce85d882e594a1a1782e
llama-ubuntu-cuda-sm_100-x64.tar.xz
568 MB
sha256:2e361f210af189d2cf01afae458004b069b5b41be87390e9203fa0eaadcfafdd
llama-ubuntu-cuda-sm_120-arm64.tar.xz
563 MB
sha256:d3a69bb688c7b572302597a32897bca36e490127bbc96046655680ebb0bef1b8
llama-ubuntu-cuda-sm_120-x64.tar.xz
567 MB
sha256:e716cd9079768af1dc42514cacecb37249ecb2fe01e29acf60c4e729ce433208
llama-ubuntu-cuda-sm_75-arm64.tar.xz
563 MB
sha256:d620c4db6fb285431d43706f5b913d9fe51365567785fc0e359b2116383e4d44
llama-ubuntu-cuda-sm_75-x64.tar.xz
567 MB
sha256:e691a01ed25532c586f4a13dae6d03a4936ebff9f7409b0893e9594b1c434d6e
llama-ubuntu-cuda-sm_80-arm64.tar.xz
562 MB
sha256:6709b04a9204fc11c39b71fb9b67e3141ad08a37e06e9b4fe09a6fd3302c3e9c
llama-ubuntu-cuda-sm_80-x64.tar.xz
566 MB
sha256:5e860f8de9169062e1bcc18c1d163231302696b8178e8270806e5944c90b44fe
llama-ubuntu-cuda-sm_86-arm64.tar.xz
561 MB
sha256:d333bc345b52180da7a82236bb7176bd27dfa3ad8758df14bf8af1f9e3b478e8
llama-ubuntu-cuda-sm_86-x64.tar.xz
565 MB
sha256:92f82cc61c8cc9de1682b8ab2d7b50f880101d09db842ed5a99db26b118b8d9a
llama-ubuntu-cuda-sm_89-arm64.tar.xz
561 MB
sha256:dd3eb75d872516cc3a11d1f01a0a7068afbd37f96028d30c3253e41789825607
llama-ubuntu-cuda-sm_89-x64.tar.xz
565 MB
sha256:559dcd32b75f0f4da212e65894ced44cc8d4d869857a84809b8aae2e33a9104c
llama-ubuntu-cuda-sm_90-arm64.tar.xz
562 MB
sha256:ec8d5c67ebdd7ad2658606933f63c7c01935161e1bfe0a0ddcb625b9e541bf6d
llama-ubuntu-cuda-sm_90-x64.tar.xz
566 MB
sha256:32100d2770e75e6a5a7e5e202a9f097494aa1d168709625590c28b22db62d056
llama-windows-cuda-sm_100-x64.7z
538 MB
sha256:aa46c148a88768bcbc21351d61fb2e7f4e2ceade63ac6ef160d8413dc9be1816
llama-windows-cuda-sm_120-x64.7z
537 MB
sha256:b95585ef2a6c1dd60d22182c2df2025ff434d9452e00aa2bd91e15ccc5206cdd
llama-windows-cuda-sm_75-x64.7z
538 MB
sha256:e1fb70c6a23915c6bb7fc9caa0e4b402ce3cfc5ac94ee2f2ec240a7e02b6bc79
llama-windows-cuda-sm_80-x64.7z
537 MB
sha256:8b209ed31b07be0fef3f467189b25faa529845707a585cfe5604a3f11ab43a72
llama-windows-cuda-sm_86-x64.7z
535 MB
sha256:9f6458a6ecf5f51e42be42c7e2540247d5fc16fc4da2ae1f39ba79fcb73cd249
llama-windows-cuda-sm_89-x64.7z
535 MB
sha256:329b2f77c5faa1a45f8cd3718d0dc7b81392aba1dbc029d95e0ea0d1c462b831
llama-windows-cuda-sm_90-x64.7z
537 MB
sha256:407b1fae41a77cddeef4156fc6bae366db6658cd2fe67752062027524f8f32b1