Skip to content

Qt: Use existing card size when formatting #81

Qt: Use existing card size when formatting

Qt: Use existing card size when formatting #81

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

build.yml

on: pull_request
🐧 Linux (Clang)  /  Linux Clang Build
1m 49s
🐧 Linux (Clang) / Linux Clang Build
🐧 Linux (GCC)  /  Linux GCC Build
2m 27s
🐧 Linux (GCC) / Linux GCC Build
🍎 macOS  /  macOS Universal Build
2m 44s
🍎 macOS / macOS Universal Build
🪟 Windows x64 (Clang)  /  Windows x64 Clang Build
8m 16s
🪟 Windows x64 (Clang) / Windows x64 Clang Build
🪟 Windows x64 (MSVC)  /  Windows x64 MSVC Build
8m 31s
🪟 Windows x64 (MSVC) / Windows x64 MSVC Build
🪟 Windows ARM64 (Clang)  /  Windows ARM64 Clang Build
7m 15s
🪟 Windows ARM64 (Clang) / Windows ARM64 Clang Build
🪟 Windows ARM64 (MSVC)  /  Windows ARM64 MSVC Build
9m 3s
🪟 Windows ARM64 (MSVC) / Windows ARM64 MSVC Build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
🐧 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/
🍎 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
🪟 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-568c2e1a-AppImage
38.8 MB
sha256:5726256223435843ffe5b6aead23f9959dd480d34aae8aa9115b1287893db777
myMCpp-linux-x64-gcc-pr45-568c2e1a-AppImage
38.9 MB
sha256:1b81fd0db541163908a602a24ac3ecf0a3d2cabc85383630474d06c07f2382d6
myMCpp-macos-universal-pr45-568c2e1a
19.1 MB
sha256:8f4d4d2852da579f0a48bed3d6247f83b6534a4672b0073b93a28e1c32c90790
myMCpp-windows-arm64-clang-pr45-568c2e1a
31.5 MB
sha256:281cfba7a722a05894329250b0a219fcf7886ae6eb8dd04f75dbb12229e2fe18
myMCpp-windows-arm64-msvc-pr45-568c2e1a
30.9 MB
sha256:b61015e71c18db2178e4c917516f52f8b32dab387ee19742d98d1197551e7a1f
myMCpp-windows-x64-clang-pr45-568c2e1a
35.6 MB
sha256:1982104c07aa3d0165b6606c24178106de32e1b4c215eb687eab708439358233
myMCpp-windows-x64-msvc-pr45-568c2e1a
34.9 MB
sha256:3a1725ba34dc72328fe10d331ac1f47657db472c7fffaface92112ff32c8cc10