Skip to content

Add Delete message(s) support #145

Add Delete message(s) support

Add Delete message(s) support #145

Triggered via push April 16, 2026 05:50
Status Success
Total duration 3m 49s
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
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/

Artifacts

Produced during runtime
Name Size Digest
LlamaCpp-24494471338-Linux-arm64.7z
410 KB
sha256:cd923bb70d15aa74edd003db04a33fd94f7814b1edd47bb3eaf015de837ce5e3
LlamaCpp-24494471338-Linux-x64.7z
454 KB
sha256:05e664f21cf11037a9ee38d37bef5ac4ff838a4408a1ff1da68aa7f630d2aa62
LlamaCpp-24494471338-Windows-arm64.7z
511 KB
sha256:e6eceebcaf8eaca9ebdcaee46e21778e5b6ca1de0d48fec3ac820cb639e3754d
LlamaCpp-24494471338-Windows-x64.7z
554 KB
sha256:34e7739b4d099b667fe4bc6e5b7e0d44acf577a454691c989e9eeefe727a746a
LlamaCpp-24494471338-macOS-universal.7z
639 KB
sha256:e683dd4efa3e624f2d645cf52e8e68fd740042cf8e67a7b2f1838ce968715404
LlamaCpp.json
1.57 KB
sha256:e5afa6562b54959e31c5c97c28230b13aca451d26f6d1c65620259d95fd8c81b