Skip to content

feat(minor): customize postinstall behavior #1069

feat(minor): customize postinstall behavior

feat(minor): customize postinstall behavior #1069

Triggered via pull request March 16, 2026 04:11
Status Failure
Total duration 1h 49m 46s
Artifacts 9

build.yml

on: pull_request
Resolve next release
0s
Resolve next release
Matrix: build-binaries
Standalone tests
4m 3s
Standalone tests
Model dependent tests
1h 42m
Model dependent tests
Update documentation website - no version release
0s
Update documentation website - no version release
Release
0s
Release
Update documentation website
0s
Update documentation website
Auto-approve documentation website deployment
0s
Auto-approve documentation website deployment
Matrix: build-electron-example
Fit to window
Zoom out
Zoom in

Annotations

1 error and 14 warnings
Model dependent tests
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
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/setup-node@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 binaries - macOS arm64
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/download-artifact@v4, actions/setup-node@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 binaries - macOS arm64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build binaries - macOS arm64
cmake 4.2.3 is already installed and up-to-date. To reinstall 4.2.3, run: brew reinstall cmake
Standalone tests
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/download-artifact@v4, actions/setup-node@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 binaries - macOS x64
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/download-artifact@v4, actions/setup-node@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 binaries - macOS x64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build binaries - macOS x64
cmake 4.2.3 is already installed and up-to-date. To reinstall 4.2.3, run: brew reinstall cmake
Build binaries - Ubuntu (2)
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.15. 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 binaries - Windows (2)
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.15. 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 binaries - Windows (2)
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>0UYS3aQAAAABuuVG7siqRSr9ogBiSCpfNRE0yRURHRTA3MjEARWRnZQ==
Build binaries - Windows (2)
Failed to restore: Cache service responded with 400
Build binaries - Ubuntu (1)
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.30. 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 binaries - Windows (1)
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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.30. 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
bins-linux-1
154 MB
sha256:a7dcd30628cf3298e540c98e38d7af3adfc8a555a7faef1aad60fda97596233e
bins-linux-2
194 MB
sha256:1be6f0c9246ed7f998c94f631b7402297c36555a5ed6f150cdb17b403778ec5c
bins-mac-arm64
1.81 MB
sha256:e7bfab62297676f274be0d2c18c98294c01639e1bea1b701703573081f34c76e
bins-mac-x64
7.93 MB
sha256:e516a028adbb2b22e67df31d1119e6cb410b5b2721cd3c36a43bf3192e1012ee
bins-win-1
146 MB
sha256:3701b8e968b7b90083c12d638d9bc0a36e70aa320322e9228db9ec5ed4d21895
bins-win-2
192 MB
sha256:4a69ca21c76cb12075adad41f94fbd0bcfba78f32e1e669a977e5ccf9f72fa3f
build
877 KB
sha256:e85d22c98d5375c4e40d18e8c6cd74d86ebd4b5400463e862c11bf98a176e49f
build-templates
32.6 KB
sha256:a3a069bf5f4abe5e7e55f8892960f964a13c2ada104a29b7833b36f8b1bf1be6
llama.cpp
265 MB
sha256:90363ee81935da663e38fca1d709ee14d53af0cebb555aa70db8e1c1c4e28631