Skip to content

CI-windows.yml: added windows-2025-vs2026 / removed explicit CMake generator #1332

CI-windows.yml: added windows-2025-vs2026 / removed explicit CMake generator

CI-windows.yml: added windows-2025-vs2026 / removed explicit CMake generator #1332

Triggered via pull request April 7, 2026 08:13
Status Cancelled
Total duration 1m 42s
Artifacts

CI-windows.yml

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

Annotations

11 errors and 3 warnings
build (windows-2025-vs2026, Debug, Visual Studio 18 2026, slnx)
Process completed with exit code 1.
build (windows-2025, Release, Visual Studio 17 2022, sln)
The run was canceled by @firewave.
build (windows-11-arm, Debug, Visual Studio 17 2022, sln)
The run was canceled by @firewave.
build (windows-2025, Debug, Visual Studio 17 2022, sln)
The run was canceled by @firewave.
build (windows-2022, Release, Visual Studio 17 2022, sln)
The run was canceled by @firewave.
build (windows-2022, Release, Visual Studio 17 2022, sln)
The operation was canceled.
CI-windows
The run was canceled by @firewave.
build (windows-2022, Debug, Visual Studio 17 2022, sln)
The run was canceled by @firewave.
build (windows-2022, Debug, Visual Studio 17 2022, sln)
The operation was canceled.
build (windows-2025-vs2026, Debug, Visual Studio 18 2026, slnx)
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, Visual Studio 17 2022, sln)
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, Debug, Visual Studio 17 2022, sln)
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/