[DISKPART] Add help text for the gpt command #4341
DarkFire01build.yml
on: push
MSBuild (i386)
25m 55s
Matrix: build-clang-cl
Matrix: build-linux
Matrix: build-msvc-arm
Matrix: build-msvc
Annotations
3 errors and 33 warnings
|
build-linux (gcc, amd64, Release, 0x502)
Process completed with exit code 127.
|
|
build-linux (clang, i386, Release, 0x502)
Process completed with exit code 127.
|
|
build-linux (gcc, amd64, Debug, 0x502)
Process completed with exit code 127.
|
|
build-msvc-arm (windows-latest, 14, arm64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-latest, 14, arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-latest, 14.29, arm64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-2022, 14.29, arm, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-2022, 14.29, arm, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-2022, 14, arm, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-2022, 14, arm, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14, amd64, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14, i386, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-clang-cl (amd64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14.2, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14.2, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc-arm (windows-latest, 14.29, arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-linux (gcc, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
build-linux (clang, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
build-msvc (windows-latest, 14, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-linux (gcc, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
build-clang-cl (i386, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-clang-cl (amd64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-clang-cl (i386, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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/
|
|
MSBuild (i386)
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@v1. 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-msvc (windows-latest, 14.2, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-msvc (windows-latest, 14.2, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. 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-linux (gcc, amd64, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (clang, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (gcc, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (gcc, i386, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (gcc, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (clang, i386, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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-linux (clang, amd64, Debug, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
reactos-clang-amd64-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
459 MB |
sha256:ea49269bf1b7c3521f118ce6ef1fa8d294d5f959f45781814022e2925acaef4a
|
|
|
reactos-clang-amd64-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
173 MB |
sha256:275576ff908a9543174aeade776befe6275d3280fff77fc250dc18b7598a3793
|
|
|
reactos-clang-cl-amd64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
143 MB |
sha256:7cc30338201d3763168468499e3fb8b14f08d66d876b1e44b539af2e84806e83
|
|
|
reactos-clang-cl-amd64-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
133 MB |
sha256:7aa7761397bc2efbfb095ed0fc38c1dbd6888f33c2d0e5c26d1f0f7759fda8c6
|
|
|
reactos-clang-cl-i386-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
145 MB |
sha256:4e3135ce24eb2e33628eb5f996f9eacbd60cc3f910800aa4eb4551b633940f98
|
|
|
reactos-clang-cl-i386-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
132 MB |
sha256:0e6583147e9d612548815b022d9348b07b4da61704bcfe56ace77096bc2e9140
|
|
|
reactos-clang-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
214 MB |
sha256:9ea47474f873347649644dc5ab254ac9d4bb5369c9548fe9f216d66f42f7ccd9
|
|
|
reactos-gcc-amd64-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
428 MB |
sha256:177605a23468e835025ae391fd60c8be60ffc4289c65fd671dc9e3f8f1078e97
|
|
|
reactos-gcc-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
205 MB |
sha256:48edbca5acdab46edfd408021c8906c58ae6f4bf009f2d9bf94c706da725986f
|
|
|
reactos-gcc-i386-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
206 MB |
sha256:798c6ce66f7bc4fda13ab3548611f1927192294658bd1c16905c0335385275e2
|
|
|
reactos-gcc-i386-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
192 MB |
sha256:3e49ff91f9da7f3789d56a5444c7b990c1fead100500fb8b25d43f85649d40fd
|
|
|
reactos-msvc14-amd64-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
150 MB |
sha256:c5594e004a7f55fe4ff8670ea1addbc65eb52398dee768638e642ce1e4e125ad
|
|
|
reactos-msvc14-amd64-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
150 MB |
sha256:47c66dbaac835ca019997e67e38439649535aa2677eda75d6ffa355e4ef2eb47
|
|
|
reactos-msvc14-amd64-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
138 MB |
sha256:91feecc76d36c1e68fd8c6b036631d9d788eb02a1651fc05a3ac15e858940770
|
|
|
reactos-msvc14-arm-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
12.7 MB |
sha256:2cb3e53dc31672b2a40fa73b701872e08e91437b8f048d4bde974d63c105d6f0
|
|
|
reactos-msvc14-arm-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
10.7 MB |
sha256:7766da9f8c0fdf5992add35f78dd9efb2e1bb24caba3c003d32dadf8f8a545c5
|
|
|
reactos-msvc14-arm64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
3.2 MB |
sha256:ac1dc3e4c5778528a40dacbe59822407af5a948cc31a4230e7242a4ca036c5b4
|
|
|
reactos-msvc14-arm64-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
3.08 MB |
sha256:623df325e05194359991d93fcad6ef2e90ee33e6d86f36f94dcf6063b7a88e8d
|
|
|
reactos-msvc14-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
154 MB |
sha256:af554f344caf642d45f3fcfe0c90314015d15185222857286f3017d5dd10c74c
|
|
|
reactos-msvc14-i386-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
154 MB |
sha256:a45ee4d359d13852018c208f578d8b1a4ea35f688b8f2c5c796443772efbeeef
|
|
|
reactos-msvc14-i386-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
130 MB |
sha256:84aea052698393f867219a6359a5cc94581a67eb32dc84a508d66d60690e275d
|
|
|
reactos-msvc14.2-amd64-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
150 MB |
sha256:4e81e2100aac00245d99fc1723075068dfb15d309604a50e212f127dc3717a39
|
|
|
reactos-msvc14.2-amd64-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
138 MB |
sha256:fb21e1c95c789dc508853e379fa99187768ac55b2352c60bc48c799932243d8d
|
|
|
reactos-msvc14.2-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
153 MB |
sha256:a7ae061fc814d4669221da8d6ddd5c45a5175e97074ebb48a5e0bb077ea838f9
|
|
|
reactos-msvc14.2-i386-Release-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
130 MB |
sha256:70ab86c58ce69dbee69368ac128466e3264865360266c1db0a021a717526cd7a
|
|
|
reactos-msvc14.29-arm-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
12.7 MB |
sha256:25f5d298a3abfe5b47fb369b3b1cf61e0422651a69f2bd7b7a250140f312b985
|
|
|
reactos-msvc14.29-arm-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
10.7 MB |
sha256:fc60a75fc9b0fdee260006e45c78f92e91f1b877a0d98779f8e1d3858ae8eeb0
|
|
|
reactos-msvc14.29-arm64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
3.19 MB |
sha256:6ce5ccaa6a41314fff1f9270ea00fdd6b3a0da679a01383f0c3d36f19cbe3ce5
|
|
|
reactos-msvc14.29-arm64-Release-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
3.06 MB |
sha256:586d566a217f12a78db1153ed8c3da7fa45bc4846886c9b8ef1f5245b464350f
|
|
|
reactos-syms-clang-cl-amd64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
101 MB |
sha256:d5a4188328a73f6c9d89607049693ccbe81e248d3e5c25130afca9dbf3c619a4
|
|
|
reactos-syms-clang-cl-i386-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
111 MB |
sha256:15f440a8189b491c1593605e0d6d6f3e444bfe2d88ef1b3c0d4e3a54ca7b7556
|
|
|
reactos-syms-msvc14-amd64-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
222 MB |
sha256:493a671b2d68cfd6f76e4bf23eeec496b14cc25067062b3279fb5a62649a9e36
|
|
|
reactos-syms-msvc14-amd64-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
223 MB |
sha256:3d8ddbd9e11a43d071565eadd1f18235c48b67da12485a090a7680a3aedaea7b
|
|
|
reactos-syms-msvc14-arm-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
54.1 MB |
sha256:7c294c6542df1d07da7b52ea7ea92bca75fc43bb40d78fb79c3f8ffa03294f3e
|
|
|
reactos-syms-msvc14-arm64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
7.69 MB |
sha256:b6d4d6d5759294695f8445f08a38ddbfab464461fa1460123a380789a5edfd33
|
|
|
reactos-syms-msvc14-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
229 MB |
sha256:0465f141ae33331146e05780beea8474600afcac503c84447520d7233e12dd98
|
|
|
reactos-syms-msvc14-i386-Debug-0x600-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
229 MB |
sha256:f9f67c3c7ba5c84d4159810d6205b97a6a4523cb8745b0db71fc1489521e0624
|
|
|
reactos-syms-msvc14.2-amd64-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
208 MB |
sha256:a44e79636f5b146fb0097ebd09cfad71fe96230c259f6141fcadbbe0d45f1f32
|
|
|
reactos-syms-msvc14.2-i386-Debug-0x502-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
214 MB |
sha256:79636c65f4136225df155d812aa810431442da96911b07959ddd167655f97e5e
|
|
|
reactos-syms-msvc14.29-arm-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
49.9 MB |
sha256:b42dcad6087638192c613d0c16c858e8c60aa82f33108ee50ca51ce67b5f355e
|
|
|
reactos-syms-msvc14.29-arm64-Debug-cb8278b5f38d77b4bd77e549dec719a929dd820d
|
7.3 MB |
sha256:e787dd87dc6f33dd0f938311e4b65bcd131039e9b04132e21d1328e73556ebc4
|
|