Skip to content

Add Delete message(s) support #146

Add Delete message(s) support

Add Delete message(s) support #146

Triggered via push April 16, 2026 05:55
Status Success
Total duration 4m 51s
Artifacts 6

build_cmake.yml

on: push
Matrix: build
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Ubuntu Latest GCC 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/upload-artifact@v4, qt-creator/install-dev-package@v2.1. 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/
Ubuntu Latest GCC
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, qt-creator/install-dev-package@v2.1. 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/
macOS Latest Clang
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, qt-creator/install-dev-package@v2.1. 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/
Windows Latest MSVC 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/upload-artifact@v4, qt-creator/install-dev-package@v2.1. 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/
Windows Latest MSVC
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, qt-creator/install-dev-package@v2.1. 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/

Artifacts

Produced during runtime
Name Size Digest
LlamaCpp-24494607349-Linux-arm64.7z
411 KB
sha256:98a22995a8962b933c2341afc8d5e13688651e6d7c482792e1402b8c5dcada25
LlamaCpp-24494607349-Linux-x64.7z
454 KB
sha256:0333f463324804b5806bb9a9241d98482a60389892a2a67ef25daa4f26737142
LlamaCpp-24494607349-Windows-arm64.7z
511 KB
sha256:1e1073d2472804e42d075c6df53ed4aa63567504cc41e1a361a83ada45caa302
LlamaCpp-24494607349-Windows-x64.7z
554 KB
sha256:6dc361f36b936b0e75ec60a083fa53de75e79889328933c568d22b90b9912ab1
LlamaCpp-24494607349-macOS-universal.7z
639 KB
sha256:a86d0bd0e2d53aa5da96fa213c2bfe372d40ba4a577d2e337c6777acfac4cdb5
LlamaCpp.json
1.57 KB
sha256:b770500be0bd41ee4386232d1d538219fc907b8dd27530dd962727915daa6d21