Skip to content

Plugin: rename CParameterOperate::GetGlobalParameters to CParameterOp… #5778

Plugin: rename CParameterOperate::GetGlobalParameters to CParameterOp…

Plugin: rename CParameterOperate::GetGlobalParameters to CParameterOp… #5778

Triggered via push March 29, 2026 02:35
Status Success
Total duration 43m 29s
Artifacts 34

build.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 17s
doxygen / build_doxygen
snap  /  build_snap
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
Fit to window
Zoom out
Zoom in

Annotations

202 warnings
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/
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/
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/
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/
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, 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/
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
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, 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/
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
No files were found with the provided path: /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v1.0.0-dev_macos-14.zip #/Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v1.0.0-dev_macos-14_bundle.zip /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/update_macos_6.9.3.json /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v1.0.0-dev_macos-14.dmg. No artifacts will be uploaded.
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
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
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/
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/
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/
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/
android / build_android (android_x86_64, x64-android, x86_64, 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, 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/
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
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, ...
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, ...
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
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, 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/
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 "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
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)
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)
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.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, 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/
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 "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
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)
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)
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_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, 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/
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
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, 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/
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/
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 (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, 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 (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/
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/
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, 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/
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
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
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, 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/
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...
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
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/
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...
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
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/
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, 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/
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
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
deploy
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/download-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
RabbitRemoteControl_v1.0.0-dev_Linux_aarch64-aarch64.flatpak Expired
86.3 MB
sha256:38688c8b5da074530bcb17918f75bb85764a7025e7a07ac0990d1960ec6757a0
RabbitRemoteControl_v1.0.0-dev_Linux_x86_64-x86_64.flatpak Expired
96.7 MB
sha256:6152e8ffabbd41812496d865d29346cd2fc3dde3164012fb442631984f6de49f
build_android_6.10.3_android_arm64_v8a Expired
35.1 MB
sha256:34fccc1cab4e4f3859164bc95a4d845c5a6f2ed0a6eef88176abe26a0015d1f0
build_android_6.10.3_android_x86_64 Expired
34.8 MB
sha256:40e1fcd2944493f33a10d9879c3608f6ad7533243ceee0270292cf73976533a5
build_android_6.11.0_android_arm64_v8a Expired
33.7 MB
sha256:55cf8e22f31d8f048031af7dc827fae6f2b2252bf25f5529b38e60f002da904a
build_android_6.11.0_android_x86_64 Expired
33.9 MB
sha256:c6f652a5e78e5eb12a4ae0570abf090ea549d712599e12bd7d8e098922920b55
build_docker_appimage_ubuntu_25.04_ubuntu-24.04 Expired
204 MB
sha256:28379da76904b0681b1301ba06797c7fe112792c4dddbf6c604d0324004959e8
build_docker_appimage_ubuntu_25.04_ubuntu-24.04-arm Expired
189 MB
sha256:4347966e095f93a005d9389bfbcee46e4f9934e8c760a7d21dde41125df29ec6
build_docker_deb_debian_12_ubuntu-24.04 Expired
2.52 MB
sha256:efe344ecdd69c6cebc69cdf4e63f993a6b29bd41847d2ed777488abcfb76b332
build_docker_deb_debian_12_ubuntu-24.04-arm Expired
2.27 MB
sha256:d55289e639e791b4875a95ccad00748e94f5edb3ca9f2e319155cd5a8123bb88
build_docker_deb_debian_13_ubuntu-24.04 Expired
2.67 MB
sha256:ec3c56912e779bf815183142a63c1e19174da81f9d354180958cfaa32caa5c8b
build_docker_deb_debian_13_ubuntu-24.04-arm Expired
2.39 MB
sha256:d060ddf731a4d00f3cb841fb5e98a7066c4f43e6914dd2f2039ec78be0b71fac
build_docker_deb_ubuntu_25.04_ubuntu-24.04 Expired
2.84 MB
sha256:9ce04b906a1bab9998f0f9eaa2bdefc6d4209710b402f2eecdd11fa91bd35aff
build_docker_deb_ubuntu_25.04_ubuntu-24.04-arm Expired
2.69 MB
sha256:22447ceec695cc7f411722cbb0f65c3e76c7cbdc5e43249be8dc60b454588ded
build_docker_deb_ubuntu_26.04_ubuntu-24.04 Expired
2.9 MB
sha256:d82c23b693e3138200dbba498e7bc06b8dd19210e2e43ce056d80125c1a55cf9
build_docker_deb_ubuntu_26.04_ubuntu-24.04-arm Expired
2.75 MB
sha256:50c9b74a1081d2d7eed262e463408ffb335c44f4886e33c2b8c6cb136d383f29
build_docker_rpm_fedora_41_ubuntu-24.04 Expired
2.63 MB
sha256:3bb096973448606a6ae1ff9a29624940bc175031007aa115f5b3f7653e02d363
build_docker_rpm_fedora_41_ubuntu-24.04-arm Expired
2.48 MB
sha256:19611be7bb5aefd1688bd353d3ea94ff3c0dfa0e283d0469c3cd121660bae65c
build_docker_rpm_fedora_42_ubuntu-24.04 Expired
2.69 MB
sha256:8cf7a80cfa7037c8692a6f48487c31ad3b3dbd822edd052a8cba336478c94812
build_docker_rpm_fedora_42_ubuntu-24.04-arm Expired
2.54 MB
sha256:e7a2bc894ee91165a544d2dae19decbc9023de4035ec933949bf4d01d598004b
build_docker_rpm_fedora_43_ubuntu-24.04 Expired
2.69 MB
sha256:ffa22c6f7f96b048f3f0c96ac5f068f88ffac6a6622cda0d028ceedef00ff2c7
build_docker_rpm_fedora_43_ubuntu-24.04-arm Expired
2.54 MB
sha256:bf3704f19462deb7a94d2c662e5c1432b493d018795716109f163f08172984ba
build_doxygen Expired
74.5 MB
sha256:2a47dad07ccda995d78f03d5b5bd90809fb132a2b92ad40b2775f5111ad0962e
build_linux_ubuntu-24.04-arm_deb Expired
2.55 MB
sha256:be325653e1640db4e635d6cc72fa9b5bfcaadaf4d5fed0903843151303c55902
build_linux_ubuntu-24.04_deb Expired
2.71 MB
sha256:8544a51753a605c06bca919ed823b64200304c06c7fed522f3a16c490add9491
build_macos_6.9.3_clang_64_macos-14_false Expired
539 MB
sha256:392c71a99f9c6012de5552b4e506bc5b6501634365a60db1d32c0e8eefce9448
build_macos_6.9.3_clang_64_macos-15-intel_false Expired
539 MB
sha256:1fe25fe260fc80e8b3ec83a24b723c1471f98c8e8341b8867a710430f20d04dc
build_macos_6.9.3_clang_64_macos-15_false Expired
540 MB
sha256:facd61138a0cd835d3bba51921e9a40e5ddb00e53aa32e564b2cb75dd7bdd22c
build_macos_macos-14 Expired
3.42 MB
sha256:df2495e0676fc43cd488a7e7ec83543f7f560dfc21bb4e4c22b56c49daade869
build_macos_macos-15 Expired
3.41 MB
sha256:a2218f37983537685385b69a81b6db126ae46a1149e7db3074beaa57f902163f
build_macos_macos-15-intel Expired
3.48 MB
sha256:1ca3dbd34972b799a570132e78de4621e0325b32d74318d4d9101230e505fdcc
build_msvc_5.15.2_win32_msvc2019 Expired
63.2 MB
sha256:d6bf68132a3a406eeaca79a2c805fb9d3778c7bfa0fdb60c45bc109299589d72
build_msvc_6.10.3_win64_msvc2022_64 Expired
136 MB
sha256:ef952f8a73971e68aee3968d33b0a10947c0ae96995f35a659978967d91c6d36
build_msvc_6.10.3_win64_msvc2022_arm64 Expired
28.9 MB
sha256:db65385b67d703eac70a81ba77bc7fe9f2693b05d658c3837076f6a42f6e0a94