Skip to content

Release v0.1.0-bate8 #5732

Release v0.1.0-bate8

Release v0.1.0-bate8 #5732

Triggered via push March 26, 2026 02:51
Status Success
Total duration 1h 56m 21s
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 15s
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

201 warnings
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/
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. 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
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. 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/
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. 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. 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. 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
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. 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
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. 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
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/
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
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. 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, 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. 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
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 (rpm, fedora, 42, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
docker / build_docker (rpm, fedora, 41, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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/
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. 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. 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. 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. 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. 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
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/
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. 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_v0.1.0-bate8_macos-14.zip #/Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v0.1.0-bate8_macos-14_bundle.zip /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/update_macos_6.9.3.json /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v0.1.0-bate8_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
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. 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
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macos_script / build_macos (x64-osx, macos-15-intel)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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 (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/
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. 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
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
docker / build_docker (appimage, ubuntu, 25.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
docker / build_docker (rpm, fedora, 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, debian, 12, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macos_script / build_macos (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. 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. 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
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. 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_v0.1.0-bate8_Linux_aarch64-aarch64.flatpak Expired
86.3 MB
sha256:ac8035b66cccccbd7c68e7e73944851a497edf3f263657639418ca93516d35ae
RabbitRemoteControl_v0.1.0-bate8_Linux_x86_64-x86_64.flatpak Expired
96.7 MB
sha256:910db6b1917b5c94151e17457917bcd3a92a0bc47f10fbedbfaac325e9e739a8
build_android_6.10.3_android_arm64_v8a Expired
35.1 MB
sha256:331fdb6279122f1dbf4e3905d7ceab7cca21e89d2015ba2f5935a40ab4d9515d
build_android_6.10.3_android_x86_64 Expired
34.8 MB
sha256:ba33260fa3cff6ad973ee500a605b75154b16e7e4ba0280ea59a9751e55c974f
build_android_6.11.0_android_arm64_v8a Expired
33.7 MB
sha256:3457fafbdeb3e475586ee165963e4347bc120a4f61db7ce76729cc25695bf904
build_android_6.11.0_android_x86_64 Expired
33.9 MB
sha256:c00935f201ecb702cee9f85121805d9fc40926bb1ecde2673367aa500adcc8da
build_docker_appimage_ubuntu_25.04_ubuntu-24.04 Expired
204 MB
sha256:59a1d3733a0a00a9cd0456a35f771a6d9a45ae47d448b08816d676dc17bce692
build_docker_appimage_ubuntu_25.04_ubuntu-24.04-arm Expired
189 MB
sha256:413ccd703a31601822190d3eccd959d35cde9f669dbdb8745878167b301593dc
build_docker_deb_debian_12_ubuntu-24.04 Expired
2.52 MB
sha256:896fd2f12a864ca09cfcdb8903b61079e5c8a3ebded0ba490db2886ae414fed9
build_docker_deb_debian_12_ubuntu-24.04-arm Expired
2.27 MB
sha256:69e2713b7e18fd825cf25c4ce30774ccdcfb4a22c0407ed7d2d29d829d1a448f
build_docker_deb_debian_13_ubuntu-24.04 Expired
2.67 MB
sha256:471ec9b38cccd08a83879e91ae3d6ebd35667ac2626367d73c10aa1513b39c81
build_docker_deb_debian_13_ubuntu-24.04-arm Expired
2.39 MB
sha256:348a233df8e235ad3457c0765eb3b77b3a495c5962c9d5f3a0e0711341123412
build_docker_deb_ubuntu_25.04_ubuntu-24.04 Expired
2.84 MB
sha256:43b91a52ee503e692b8eb0ee1cc58347cbef457b8db63b8eac77d5785d3f80be
build_docker_deb_ubuntu_25.04_ubuntu-24.04-arm Expired
2.69 MB
sha256:cb015b0c538e94e8b630dfbceda4882dff1a290686cd49a1d653ecbb1f562f11
build_docker_deb_ubuntu_26.04_ubuntu-24.04 Expired
2.9 MB
sha256:884585159aecb2c29e3b3edf466b11b88081b4c9aaf9d2c5027c2a4466113b0f
build_docker_deb_ubuntu_26.04_ubuntu-24.04-arm Expired
2.75 MB
sha256:01b98d3ead77d303c9fafef333603680a43faeec774af253196d56b3ea2a1c49
build_docker_rpm_fedora_41_ubuntu-24.04 Expired
2.63 MB
sha256:d7d7a40716681fd7887c1a8fe95b9d9ad9fa6f5fa031048684d3ab191adbd7cc
build_docker_rpm_fedora_41_ubuntu-24.04-arm Expired
2.48 MB
sha256:e7f4585e80eb244b28a181394f953b233fd06c018baaf887a1a538ee8948f8bd
build_docker_rpm_fedora_42_ubuntu-24.04 Expired
2.69 MB
sha256:08d670d60b5e6a06f0911630e2ebaafe2f3a8dd5f95ca4e9db06e2b214302144
build_docker_rpm_fedora_42_ubuntu-24.04-arm Expired
2.54 MB
sha256:de674c9c8c6e7ebfd2bcae009414c22692e457759323f313fb9f066f7216bbab
build_docker_rpm_fedora_43_ubuntu-24.04 Expired
2.69 MB
sha256:8234add2f0ff32e634c390e98a21e2540d9b36cf8793e1893275e338c365cf2d
build_docker_rpm_fedora_43_ubuntu-24.04-arm Expired
2.54 MB
sha256:1822b69884eac89f249b63a3b8de41fff8d62437733413ff59de8dd92f896202
build_doxygen Expired
74.5 MB
sha256:e201cb3bc393f40649d8747a0fa60f63239436ed23e57af260ea0317d1392a3b
build_linux_ubuntu-24.04-arm_deb Expired
2.55 MB
sha256:0fffe3174a951f93fee6533aafa177b93d1fe2167ea43aade9bb6726e0d8341a
build_linux_ubuntu-24.04_deb Expired
2.71 MB
sha256:717670ef063e15b117b7e8f162931f807d588835310137131f936108157c0b3a
build_macos_6.9.3_clang_64_macos-14_false Expired
539 MB
sha256:57f347533a8c118495d0ae611e5435c02d1d854cfb31f862782ed7f7dc2cc758
build_macos_6.9.3_clang_64_macos-15-intel_false Expired
539 MB
sha256:6f3ebd7ee7c8ad8431e8eedbfda929ce4af1652d55375aa75989333d359d2e99
build_macos_6.9.3_clang_64_macos-15_false Expired
540 MB
sha256:3cb4bd5fc2b623d2d2b8abc64878ce29fb0c979d59ff08f7a99ccc105a986c07
build_macos_macos-14 Expired
3.42 MB
sha256:416d6d80acfdc17163cb6106814c649880b9bd69039aff43aa0bcfe6c67b1d89
build_macos_macos-15 Expired
3.41 MB
sha256:90b64455691678ed1f3fce83968691a655bb38a094e196cf7ff9f6ac7ebc2b17
build_macos_macos-15-intel Expired
3.48 MB
sha256:013f0437d7e570943ec424043d1b5002fb5fbf43fc6efae7bdca2a72c222c0ab
build_msvc_5.15.2_win32_msvc2019 Expired
63.2 MB
sha256:2410353f78775202f536930e76c60b950c04da0f822c8b18c9d6a65ec211e437
build_msvc_6.10.3_win64_msvc2022_64 Expired
136 MB
sha256:e310af116c07b7ec1f688cae99d554a76ae0781f9e2dddb4a870d58666e01d08
build_msvc_6.10.3_win64_msvc2022_arm64 Expired
28.9 MB
sha256:9befa0844695152bad358f277b482866053025bd3ad9eb5f758f5ff1cc1d92a2