Skip to content

CI-windows.yml: removed explicit usage of Visual Studio CMake generators #1400

CI-windows.yml: removed explicit usage of Visual Studio CMake generators

CI-windows.yml: removed explicit usage of Visual Studio CMake generators #1400

Triggered via pull request May 14, 2026 16:12
Status Cancelled
Total duration 3m 46s
Artifacts

CI-windows.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 6 warnings, and 2 notices
build (windows-2022, Release)
The run was canceled by @firewave.
build (windows-2022, Release)
The operation was canceled.
build (windows-11-arm, Debug)
The run was canceled by @firewave.
build (windows-11-arm, Debug)
The operation was canceled.
build (windows-11-arm, Release)
The run was canceled by @firewave.
build (windows-11-arm, Release)
The operation was canceled.
build (windows-2025, Release)
The run was canceled by @firewave.
build (windows-2025, Release)
The operation was canceled.
CI-windows
The run was canceled by @firewave.
build (windows-2022, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-2025, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-2022, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-11-arm, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-11-arm, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-2025, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
build (windows-2025, Debug)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
build (windows-2025, Release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026