Skip to content

[FREELDR] Retrieve and store the disk GUID signature if the disk is G… #4391

[FREELDR] Retrieve and store the disk GUID signature if the disk is G…

[FREELDR] Retrieve and store the disk GUID signature if the disk is G… #4391

Triggered via push April 9, 2026 16:00
Status Success
Total duration 2h 27m 3s
Artifacts 44

build.yml

on: push
Matrix: build-clang-cl
Matrix: build-linux
Matrix: build-msvc-arm
Matrix: build-msvc
Fit to window
Zoom out
Zoom in

Annotations

33 warnings
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-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-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-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-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.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 (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-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-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 (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/
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/
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, 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-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-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, 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 (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, 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, 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, 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-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-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-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/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 (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/
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 (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, 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 (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/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/

Artifacts

Produced during runtime
Name Size Digest
reactos-clang-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
471 MB
sha256:0799e063b636ce14ae72d44fa8bed9d696c87a9c6f90678adfff7c74c7b694c8
reactos-clang-amd64-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
174 MB
sha256:f9c5625ec294ae4a722a7d0dde540bbfe7dc82c25b085b30ce0abd65da7a4e5e
reactos-clang-cl-amd64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
144 MB
sha256:53c83cba32c3a57f9be9bdaf971919874eb76fa46cc679bd6fb4b624e4f89ff3
reactos-clang-cl-amd64-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
133 MB
sha256:ac5907d213ddf3ce9c0b7787c7355bb4e74f040b7b34c973bd1c45128dfc1e5b
reactos-clang-cl-i386-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
144 MB
sha256:e02a006b53a3deb285f8f74a4ae89344c41ed8e92007979671adfba156123665
reactos-clang-cl-i386-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
132 MB
sha256:38259e936b02816b153924a414583c4de62176b7a470c06c7923daec34b13778
reactos-clang-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
217 MB
sha256:c89adf4f114b364424fd26e61fe569ba5a3f085728670b9b662404a76a273d96
reactos-clang-i386-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
171 MB
sha256:6eeec8026c63e4de532113683e2d55cc26e36828c45ab845862a1705cdf9aa89
reactos-gcc-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
438 MB
sha256:ec88727406e3500462dd52894d5a4ee258c43b4aa94be5280dc183e12a85a9cf
reactos-gcc-amd64-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
439 MB
sha256:c7b1430b444e6b5471e8f74ccf8529586476faec0ef7220657d9e1d05b0a6162
reactos-gcc-amd64-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
177 MB
sha256:384beac7007c0c71b1a5a462816ef73325a65216e1259bfa48daa45b9752fdb5
reactos-gcc-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
208 MB
sha256:bcecc9882e9f799927f1171887276a69b5a4f7c8745bfbe3b7ce8ac85bdf5e50
reactos-gcc-i386-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
209 MB
sha256:ab18a241d3fa2aa25d265ce481bbbbb134020686ea71d4b99a2a565a5a7a677b
reactos-gcc-i386-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
191 MB
sha256:35ba0f929602c415816b5dd7f7682275d4bad162f7a1ddb203e34877c1efc473
reactos-msvc14-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
151 MB
sha256:56e79282e70c21fc96a48b1b5825ab4c22ac8fb4185aa511247816c8022d184c
reactos-msvc14-amd64-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
151 MB
sha256:5584dc8aaf0b22d62f08bc284ef8cb5a2f22dfac0b46d111d1e162f84614b22a
reactos-msvc14-amd64-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
142 MB
sha256:3bf98df66874599f3072703835ce83372db4f14311d11266dc0b5e66e0f5c7f5
reactos-msvc14-arm-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
12.7 MB
sha256:90e8cd8324522b61d970260939f35b336d172c9d92c7a98bd7c88fd5edbcffb2
reactos-msvc14-arm-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
10.8 MB
sha256:c2b94b1c6550e3d9e5653d455c84f811327b97a8d7a1c0b8834e3cf80b3e152c
reactos-msvc14-arm64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
3.21 MB
sha256:fc64ad200e91dd702a254ba4be0843b6e3a8a9855385de74e0fb3a9eadcf62d0
reactos-msvc14-arm64-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
3.09 MB
sha256:4d58fcebe3ed7eccbab16c7827d152e13bab1b3c0dfad156d1df4f3d736016c0
reactos-msvc14-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
153 MB
sha256:dea934173eb3be79b1696afe59d382e7a4349145b12448ee02d23180a1404a8d
reactos-msvc14-i386-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
154 MB
sha256:257fc02dfdcbe9c73b96070756a0025b45128a54a3b354056c48c6d28a9c049c
reactos-msvc14-i386-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
132 MB
sha256:0c4dd1bc025c9c5b22486bf4109e039276eab5fc3d255c82163e5b1faea21628
reactos-msvc14.2-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
150 MB
sha256:972eac4da7dbe1c441c0cef56eaf9b0afb10e1c7e7d3fa1ce26fc9c33a220366
reactos-msvc14.2-amd64-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
142 MB
sha256:ff976fcd6860af42662777d17d05d83eb230ea6321a5931b5ef01dd2885afa09
reactos-msvc14.2-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
153 MB
sha256:1333f1448872fd6ab36493908c7c5ba319a0527b48225db57d54ffa483c60a60
reactos-msvc14.2-i386-Release-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
132 MB
sha256:b78aaa8ef5617047a9d35de85485ce5df86e2d3c9596da3f9ac34508b2257c32
reactos-msvc14.29-arm-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
12.7 MB
sha256:6d0482905e93d291bfb6376211c0e190deb11a537a6ec6f6c017264ef9e6cef9
reactos-msvc14.29-arm-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
10.8 MB
sha256:c81c57b461828e88e6c8adc13736b1c52e6c54a3c9a82b137f514cd69e51b963
reactos-msvc14.29-arm64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
3.2 MB
sha256:51539b5fb9908280fdab765df6c138a3bb9076be6ce3f584de15d5d2b854137a
reactos-msvc14.29-arm64-Release-7779fb44597a0892c6b1d76f40a6179ca9eccf45
3.07 MB
sha256:6d96bf74c935c501d3933559791fe17438c11a7ea4bcfdf64263b5d546f54bdd
reactos-syms-clang-cl-amd64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
104 MB
sha256:28d3534a46180ca3d222d6d40ff2e4ce5cba59e24d34c30ba1548215ca3b92ed
reactos-syms-clang-cl-i386-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
112 MB
sha256:4e2226040f33bb6ed441dca2b60cdfcd379c1394ad58ed9afdddbf8a87c3f906
reactos-syms-msvc14-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
228 MB
sha256:558e1cbbf8f739ed93afc6f291c025b0ec9d627013fb25d7d2615381f594d829
reactos-syms-msvc14-amd64-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
228 MB
sha256:6d8b94d9e0b006e9a2856b33b6c9921b4d9beb3c7dbaf957ec99c812b33237e2
reactos-syms-msvc14-arm-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
54.6 MB
sha256:65ccb956aa34a409c31a777ceaa9d9133a74a18caf2633641075b070fd9080f8
reactos-syms-msvc14-arm64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
7.84 MB
sha256:79ead2f192d28a39ac7b0633b9556abd1f00b491d35377d98e1ef54c294a0827
reactos-syms-msvc14-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
233 MB
sha256:9de418bcb9ad10f2ffc47d370ec77d4738f01047232158827f11a96d42b034ad
reactos-syms-msvc14-i386-Debug-0x600-7779fb44597a0892c6b1d76f40a6179ca9eccf45
234 MB
sha256:7e89be958536a84043ab0632de32bf33aa621883f94dc79be825c3901537769f
reactos-syms-msvc14.2-amd64-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
212 MB
sha256:dd01a9fdca97a27234a314e61ef4fc8ef393205831b189911b2be1ed50498eca
reactos-syms-msvc14.2-i386-Debug-0x502-7779fb44597a0892c6b1d76f40a6179ca9eccf45
217 MB
sha256:bc1d86d4ecee76dc2dc0e038b35e5480e0e3966ae4c4d56fc443a8b592f42ec2
reactos-syms-msvc14.29-arm-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
50.2 MB
sha256:14678ea627a3fb799f824e2fc789a2a9bcdcdf32115699948314f960acc78e46
reactos-syms-msvc14.29-arm64-Debug-7779fb44597a0892c6b1d76f40a6179ca9eccf45
7.4 MB
sha256:a02238bc1837464b8d1e62b8b6d3d37e09565d03f4240dcbb7b17246a4aaedb2