App: modify size policy #5787
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 22s
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
19 errors and 99 warnings
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
Process completed with exit code 1.
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
vcpkg install failed. See logs for more information:
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
Download failed, halting portfile.
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
Download failed, halting portfile.
|
|
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-15_6_9_3_" failed
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
The operation was canceled.
|
|
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-15_6_9_3_" failed
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
The operation was canceled.
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
The strategy configuration was canceled because "macos.build_macos.arm64-osx_macos-15_6_9_3_" failed
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
The operation was canceled.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
Process completed with exit code 1.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
vcpkg install failed. See logs for more information:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
Download failed, halting portfile.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, 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_x86_64_x64-androi" 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_x86_64_x64-androi" failed
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
The operation was canceled.
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
The strategy configuration was canceled because "android.build_android.android_x86_64_x64-androi" failed
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
The operation was canceled.
|
|
macos / build_macos (arm64-osx, macos-15, 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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
macos / build_macos (arm64-osx, macos-15, 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 (arm64-osx, macos-15, 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 (arm64-osx, macos-15, 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)
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/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
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
|
|
macos / build_macos (arm64-osx, macos-14, 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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
macos / build_macos (arm64-osx, macos-14, 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 (arm64-osx, macos-14, 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 (arm64-osx, macos-14, 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 (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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
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
|
|
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_x86_64, x64-android, x86_64, 6.11.0, 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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
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/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, 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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
.cache/tools/qt/Qt/6.11.0/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L339
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
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, actions/setup-python@v5, jurplel/install-qt-action/action@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/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
.cache/tools/qt/Qt/6.10.3/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L335
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
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/
|
|
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/
|
|
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, 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/
|
|
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 (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 (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/
|
|
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/
|
|
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 (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/
|
|
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, actions/setup-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'netapi32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...:
build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
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.
|
|
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/
|
|
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)
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-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-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-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 (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 (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/
|
|
flatpak / build_flatpak (aarch64, 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/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 (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, actions/setup-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...:
build/vcpkg_installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...:
build/vcpkg_installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
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/
|
|
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 (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, actions/setup-python@v5, actions/upload-artifact@v4, jurplel/install-qt-action/action@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/
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Ws2_32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'netapi32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...:
build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
RabbitRemoteControl_v0.1.0-dev_Linux_aarch64-aarch64.flatpak
Expired
|
86.3 MB |
sha256:09ffe8604e2243fb5227df25fdbc971872d45a2b524aeffde802b63fed4b5f93
|
|
|
RabbitRemoteControl_v0.1.0-dev_Linux_x86_64-x86_64.flatpak
Expired
|
96.9 MB |
sha256:33e6cfe395188390a4dd639af9c43709dcbb0e770b0e2336eab63af33ab0b5b1
|
|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04
Expired
|
204 MB |
sha256:7f7f9ffdf83293455cce0e0428127d3174eb82851e9fffa9da4c85410beac140
|
|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
189 MB |
sha256:b3f2b9d190d9435266d67475225a366fbf20573b887fe389f51a331748419997
|
|
|
build_docker_deb_debian_12_ubuntu-24.04
Expired
|
2.52 MB |
sha256:b1d68ef3d86d29f4c3efb370050be9660bec5d6ce413296477e84a23229f1faa
|
|
|
build_docker_deb_debian_12_ubuntu-24.04-arm
Expired
|
2.27 MB |
sha256:b4d01997143ace3e0910d15d7574cc2679d980fb1fb1bec1a602abcbcb9bd6cf
|
|
|
build_docker_deb_debian_13_ubuntu-24.04
Expired
|
2.67 MB |
sha256:2f117f9b5ad09ac8490a218c4989515c73f9cfa75d35a47235885cc71e3d2853
|
|
|
build_docker_deb_debian_13_ubuntu-24.04-arm
Expired
|
2.39 MB |
sha256:9a97083bbce7d863f5b79056bbd6626733e71c70ed1bed6e3c0171cbf052fd4d
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04
Expired
|
2.84 MB |
sha256:9fc7bf6ac7b6928c587e6212a7c3a9546e711980b24430dc2092b30027c8f2b0
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
2.69 MB |
sha256:8a9570ff9ad9f1cd55be4965cb6b1b9178f123cb11abd605773428d2f966f54b
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04
Expired
|
2.9 MB |
sha256:b64c3606a1b6f008583f3bc42a8efd9ef7f5528b118aa0a1989142a6760fe1e7
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04-arm
Expired
|
2.75 MB |
sha256:1706df981dce974078f96559a808b3e3ff31827ffa211c9e1c274c84c34a7842
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04
Expired
|
2.64 MB |
sha256:80e31d6b9c0e3c4738c41f91142982c5a0123249f764058730380da6fd6199fc
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04-arm
Expired
|
2.49 MB |
sha256:2c166a4303188aee44115b329779a9ea9d05ecc97c1dd5812c59e9311fcb2837
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04
Expired
|
2.69 MB |
sha256:57a0c8b7cf1b112d66291baf4cecb4640d5454e757a35765353326a527594658
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:ae338f80dd5469b7fa4fce5793567f8054044c45472a9dc584d431b2dda48017
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04
Expired
|
2.69 MB |
sha256:cd98dadfb04d0a30c0c8ca436680a4c9df70ce0a4e8bd375a567df063610d949
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:4e134563a44aa8bccbbc482778a754a57414ebaa3b32f928394b1e24c8bb09c8
|
|
|
build_doxygen
Expired
|
74.5 MB |
sha256:1e13ca079ae0937d12aa6daffdb0c108cc8b09d8a07c52b69f98eafd2eea650e
|
|
|
build_linux_ubuntu-24.04-arm_deb
Expired
|
2.55 MB |
sha256:abec200473f368c8c5003745f3c02ebc1350ee414b1bc402be25155a0dd78470
|
|
|
build_linux_ubuntu-24.04_deb
Expired
|
2.71 MB |
sha256:8c736c9b064bc7fd9976fbf34743697cfd111ed4faf45ca08393e2a131e464ae
|
|
|
build_macos_macos-14
Expired
|
3.42 MB |
sha256:ccce053e96c2bdfa51e13a630fc7692a2dfb7c096d7eb97ebe0fa6bd4cde63b4
|
|
|
build_macos_macos-15
Expired
|
3.41 MB |
sha256:4dce8cea7f19655dbe5284aa70679765ba549b1d4fc6d0e8c61bc485c7d0e264
|
|
|
build_macos_macos-15-intel
Expired
|
3.49 MB |
sha256:5ccca14133e18815c9f805175726f100f697ad36cc3eeaa233d59d50a476d276
|
|
|
build_msvc_5.15.2_win32_msvc2019
Expired
|
63.2 MB |
sha256:6cb7a42286f28206c46c01d16b950832514baa18fbd786143341024883bf6f54
|
|
|
build_msvc_6.10.3_win64_msvc2022_64
Expired
|
136 MB |
sha256:ce6ff32a8d4d5b7c4f79d7384ccff7b6412184f5e6c38811b7e4820962c73e4f
|
|
|
build_msvc_6.10.3_win64_msvc2022_arm64
Expired
|
28.9 MB |
sha256:a33e0022fa2b63725d09bf4368180383c9eea50a4f07217f95a2b8c7b1760bf0
|
|