Script: modify script to support deepin #5800
KangLinbuild.yml
on: push
Matrix: android / build_android
Matrix: docker / build_docker
Matrix: flatpak / build_flatpak
Matrix: linux / build_linux
Matrix: macos / build_macos
Matrix: msvc / build_msvc
doxygen
/
build_doxygen
5m 47s
snap
/
build_snap
Matrix: aarch64 / build_arch
Waiting for pending jobs
Matrix: appimage / build_appimage
Waiting for pending jobs
Matrix: macos_script / build_macos
Matrix: mingw / build_mingw
Matrix: ubuntu / build_ubuntu
Waiting for pending jobs
deploy
0s
Annotations
25 errors and 40 warnings
|
flatpak / build_flatpak (aarch64, ubuntu-24.04-arm)
The strategy configuration was canceled because "flatpak.build_flatpak.x86_64_ubuntu-24_04" failed
|
|
flatpak / build_flatpak (x86_64, ubuntu-24.04)
Build failed: Error: The process '/app/bin/xvfb-run' failed with exit code 1
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
Process completed with exit code 1.
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
vcpkg install failed. See logs for more information:
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
Download failed, halting portfile.
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
Download failed, halting portfile.
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
The strategy configuration was canceled because "msvc.build_msvc.Win32_x86-windows_v143_vc" failed
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
The operation was canceled.
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
The strategy configuration was canceled because "msvc.build_msvc.Win32_x86-windows_v143_vc" failed
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
The operation was canceled.
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Process completed with exit code 1.
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
vcpkg install failed. See logs for more information:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Download failed, halting portfile.
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Download failed, halting portfile.
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
The strategy configuration was canceled because "macos.build_macos.arm64-osx_macos-14_6_9_3_" failed
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
The strategy configuration was canceled because "macos.build_macos.arm64-osx_macos-14_6_9_3_" failed
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
The strategy configuration was canceled because "macos.build_macos.arm64-osx_macos-14_6_9_3_" failed
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
The operation was canceled.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
The strategy configuration was canceled because "android.build_android.android_arm64_v8a_arm64_2" failed
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
Process completed with exit code 1.
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
vcpkg install failed. See logs for more information:
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
Download failed, halting portfile.
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
Download failed, halting portfile.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
The strategy configuration was canceled because "android.build_android.android_arm64_v8a_arm64_2" failed
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
The strategy configuration was canceled because "android.build_android.android_arm64_v8a_arm64_2" failed
|
|
flatpak / build_flatpak (x86_64, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, flathub-infra/flatpak-github-actions/flatpak-builder@master. 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/
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, lukka/run-vcpkg@v11. 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/
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
vcpkg_replace_string made no changes.
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
vcpkg_replace_string made no changes.
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, lukka/run-vcpkg@v11. 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/
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, lukka/run-vcpkg@v11. 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 / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, lukka/run-vcpkg@v11. 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 / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, lukka/run-vcpkg@v11. 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 / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
libtool 2.5.4 is already installed and up-to-date.
To reinstall 2.5.4, run:
brew reinstall libtool
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
autoconf 2.73 is already installed and up-to-date.
To reinstall 2.73, run:
brew reinstall autoconf
|
|
doxygen / build_doxygen
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, lukka/run-vcpkg@v11. 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/
|
|
linux / build_linux (Release, 6.10.3, ubuntu-24.04, deb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
mingw / build_mingw (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. 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/
|
|
linux / build_linux (Release, 6.10.3, ubuntu-24.04-arm, deb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, debian, 12, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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_script / build_macos (x64-osx, macos-15-intel)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 43, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 42, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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_script / build_macos (arm64-osx, macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, ubuntu, 26.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 43, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, debian, 13, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, ubuntu, 25.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, ubuntu, 26.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, debian, 12, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, debian, 13, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (appimage, ubuntu, 25.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (appimage, ubuntu, 25.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 41, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 42, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (rpm, fedora, 41, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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_script / build_macos (arm64-osx, macos-15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. 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/
|
|
docker / build_docker (deb, ubuntu, 25.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. 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 | |
|---|---|---|---|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04
Expired
|
204 MB |
sha256:d29e004d66ff278afc68336db0c46b6ac0fd2f6127d5eaf23f711144bd3cc54e
|
|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
189 MB |
sha256:bab955a60324d7a87b2fa9f24bc8dc9a9a8969410fa56f4f1fab83535404619a
|
|
|
build_docker_deb_debian_12_ubuntu-24.04
Expired
|
2.52 MB |
sha256:f935a6337508771977c06d584bb9b3abd3d1b8af5d704adc9a2281fc874f37a8
|
|
|
build_docker_deb_debian_12_ubuntu-24.04-arm
Expired
|
2.27 MB |
sha256:de327fa0baf386fc1a62f3a5f52e8fa976be57117f2f5e35b99e43f10f05bcc5
|
|
|
build_docker_deb_debian_13_ubuntu-24.04
Expired
|
2.67 MB |
sha256:d85509970d1871591b51af6a197f08356e8e2c6886d593d2d237f3020fd25f6a
|
|
|
build_docker_deb_debian_13_ubuntu-24.04-arm
Expired
|
2.4 MB |
sha256:1dca4a36ec02741232b586e11b05ef93bb94f001fee51b15a6448408d1b1865e
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04
Expired
|
2.84 MB |
sha256:d6d3b0f4a18644bb7c452f4113ae761813aef6bb614b4e6eeee1842ea8cc68dd
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
2.69 MB |
sha256:cb770ab2619afc76c767b413ee6316faf2ac97bcb9450fd253323c2d37e5f245
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04
Expired
|
2.9 MB |
sha256:25f99d29dd3c3f42e53a8299292d5ec8441cf235a0da66d6d3389c4dbc18b3e5
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04-arm
Expired
|
2.75 MB |
sha256:a375397c1ed648d5c6e409e25234b126429aee17c5a8ee8e75f5c700a2b29e7a
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04
Expired
|
2.64 MB |
sha256:9d452eb6f5585216e6bdba56c7197cfee890c7d555d0b6480a573e0b8a7ccb88
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04-arm
Expired
|
2.49 MB |
sha256:0bfb302988d75b4fbd425b6e54efa694cf27dd40e02ff69f3bf4ddec7cb7a6ba
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04
Expired
|
2.69 MB |
sha256:46b372bc5041f310089d3266045863c6074d092e87c5b6f4629a9631ee34be30
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:0ab5aeaffec34f7c9e3cfb6816caa07d952994a0056d5c30eeb8c552aa5bc99c
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04
Expired
|
2.69 MB |
sha256:9444fb0b0b76de9dd764440080f625b3dab8b0146e847e758bf8f37892507fea
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:9f1e5993768effff7c78efec6e20376bb1b554d28370c9d8b2cfc8200567b75e
|
|
|
build_doxygen
Expired
|
74.5 MB |
sha256:cc3c3296f1460d17770f3b57a83ee7f20c07272de09a4896ee9aeb552ebdde41
|
|
|
build_linux_ubuntu-24.04-arm_deb
Expired
|
2.55 MB |
sha256:81c8edc34137961a9b21b49e02c830c225c08ac7e836dcbab0e207e32b9a1d5e
|
|
|
build_linux_ubuntu-24.04_deb
Expired
|
2.71 MB |
sha256:fc473fa35ed7ca90400c53936b3c585a0c6ffeaf95160cd89cb74f07e469e684
|
|
|
build_macos_macos-14
Expired
|
3.42 MB |
sha256:ad48da190a6950cfab1817a35d646f90bf63bccb420f8284cf66c434ca8d1218
|
|
|
build_macos_macos-15
Expired
|
3.41 MB |
sha256:7b9f46c4238848cc7e68c27936c699063551d77eef8ded6445352c4bcaa3ab35
|
|
|
build_macos_macos-15-intel
Expired
|
3.49 MB |
sha256:2515379437590070b05c57119fc8eb133dcf266ea1b30fab22b4e2b320aa7969
|
|