2026ww16 security fixes #247
windows_2022.yml
on: pull_request
Main Trigger
/
...
/
Build
16m 28s
Annotations
5 errors and 1 warning
|
Main Trigger / CiD / Build / Build
Canceling since a higher priority waiting request for windows-pull_request-281/merge-2022 exists
|
|
Main Trigger / CiD / Build / Build
The operation was canceled.
|
|
Windows (2022)
Canceling since a higher priority waiting request for windows-pull_request-281/merge-2022 exists
|
|
Windows (2022)
Canceling since a higher priority waiting request for windows-pull_request-281/merge-2022 exists
|
|
Windows (2022)
Canceling since a higher priority waiting request for windows-pull_request-281/merge-2022 exists
|
|
Main Trigger / CiD / Build / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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/
|