Skip to content

Qt: Use existing card size when formatting #80

Qt: Use existing card size when formatting

Qt: Use existing card size when formatting #80

Triggered via pull request March 26, 2026 10:34
@SternXDSternXD
synchronize #45
fixissues
Status Success
Total duration 9m 22s
Artifacts 7

build.yml

on: pull_request
🐧 Linux (Clang)  /  Linux Clang Build
1m 59s
🐧 Linux (Clang) / Linux Clang Build
🐧 Linux (GCC)  /  Linux GCC Build
2m 23s
🐧 Linux (GCC) / Linux GCC Build
🍎 macOS  /  macOS Universal Build
1m 55s
🍎 macOS / macOS Universal Build
🪟 Windows x64 (Clang)  /  Windows x64 Clang Build
7m 48s
🪟 Windows x64 (Clang) / Windows x64 Clang Build
🪟 Windows x64 (MSVC)  /  Windows x64 MSVC Build
8m 23s
🪟 Windows x64 (MSVC) / Windows x64 MSVC Build
🪟 Windows ARM64 (Clang)  /  Windows ARM64 Clang Build
7m 8s
🪟 Windows ARM64 (Clang) / Windows ARM64 Clang Build
🪟 Windows ARM64 (MSVC)  /  Windows ARM64 MSVC Build
9m 19s
🪟 Windows ARM64 (MSVC) / Windows ARM64 MSVC Build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
🍎 macOS / macOS Universal Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, jurplel/install-qt-action/action@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 / macOS Universal Build
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
🐧 Linux (Clang) / Linux Clang Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, jurplel/install-qt-action/action@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 (GCC) / Linux GCC Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, jurplel/install-qt-action/action@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/
🪟 Windows ARM64 (Clang) / Windows ARM64 Clang Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, ilammy/msvc-dev-cmd@v1.13.0, jurplel/install-qt-action/action@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/
🪟 Windows x64 (Clang) / Windows x64 Clang Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, ilammy/msvc-dev-cmd@v1.13.0, jurplel/install-qt-action/action@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/
🪟 Windows x64 (MSVC) / Windows x64 MSVC Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, ilammy/msvc-dev-cmd@v1.13.0, jurplel/install-qt-action/action@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/
🪟 Windows ARM64 (MSVC) / Windows ARM64 MSVC Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, ilammy/msvc-dev-cmd@v1.13.0, jurplel/install-qt-action/action@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
myMCpp-linux-x64-clang-pr45-d7cc99ee-AppImage
38.8 MB
sha256:431c61856e2431522efa1d549904984f7169df3386430c3644d75664f1cfc2f7
myMCpp-linux-x64-gcc-pr45-d7cc99ee-AppImage
38.9 MB
sha256:336aef892bfe071a2c4f5e1842e9598549cf46918d7bf28b66da730ca57c3895
myMCpp-macos-universal-pr45-d7cc99ee
19.1 MB
sha256:f8d25a52d29243cccb3cd67ce51556259129baf57e433d6fdfc54020a4ad36df
myMCpp-windows-arm64-clang-pr45-d7cc99ee
31.5 MB
sha256:d348046c7428692fda4ae1b00320c1d77c9d3c1cf28dc21eea3585b3e7088183
myMCpp-windows-arm64-msvc-pr45-d7cc99ee
30.9 MB
sha256:c4a5fa37fafd0ca1fbc9a5c8816f6c88a3473eabfb709be481914beb5417918f
myMCpp-windows-x64-clang-pr45-d7cc99ee
35.6 MB
sha256:aac05a33b56afed5d737b45fd77b87a8bc9ef03817a94e6ce8dae0aca39f4c3d
myMCpp-windows-x64-msvc-pr45-d7cc99ee
34.9 MB
sha256:3ae88dc4a237be51822106d5827c80c6f10e2f08e725d8f62dac1c5ee946a624