Skip to content

Release builds (Docker) (Windows Container) #42

Release builds (Docker) (Windows Container)

Release builds (Docker) (Windows Container) #42

Manually triggered March 13, 2026 09:48
Status Cancelled
Total duration 4m 34s
Artifacts

release_docker_win.yml

on: workflow_dispatch
Matrix: Release Windows Docker image
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 4 warnings
Release Windows Docker image (2022, nanoserver)
Canceling since a higher priority waiting request for Release builds (Docker) (Windows Container)-refs/heads/main exists
Release Windows Docker image (2022, nanoserver)
The operation was canceled.
Release Windows Docker image (2022, servercore)
Canceling since a higher priority waiting request for Release builds (Docker) (Windows Container)-refs/heads/main exists
Release Windows Docker image (2022, servercore)
The operation was canceled.
Release Windows Docker image (2025, servercore)
Canceling since a higher priority waiting request for Release builds (Docker) (Windows Container)-refs/heads/main exists
Release Windows Docker image (2025, servercore)
The operation was canceled.
Release Windows Docker image (2025, nanoserver)
Canceling since a higher priority waiting request for Release builds (Docker) (Windows Container)-refs/heads/main exists
Release Windows Docker image (2025, nanoserver)
The operation was canceled.
Release builds (Docker) (Windows Container)
Canceling since a higher priority waiting request for Release builds (Docker) (Windows Container)-refs/heads/main exists
Release Windows Docker image (2022, nanoserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3. 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/
Release Windows Docker image (2022, servercore)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3. 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/
Release Windows Docker image (2025, servercore)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3. 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/
Release Windows Docker image (2025, nanoserver)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3. 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/