Skip to content

[ADVAPI32] Sync crypt components to wine-10.0 #402

[ADVAPI32] Sync crypt components to wine-10.0

[ADVAPI32] Sync crypt components to wine-10.0 #402

Triggered via push April 2, 2026 21:09
Status Success
Total duration 42m 37s
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-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, 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/
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, 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, 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, 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.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, 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, 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, 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, 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 (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 (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-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-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, 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, 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/
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-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, 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, 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, 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, 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, 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/

Artifacts

Produced during runtime
Name Size Digest
reactos-clang-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
471 MB
sha256:7ad02d992f856acc238eb00a88cdd6fdec895af55ce6a539e92c5e300030529a
reactos-clang-amd64-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
174 MB
sha256:4d7f97ba87d60eab1e24cb894d9a85be429323d2d94d5d5987810997a30bba07
reactos-clang-cl-amd64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
144 MB
sha256:a9ff796c133298f266d33172fe34b86f6a29b9753cc601359e8fc18f0b40a248
reactos-clang-cl-amd64-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
133 MB
sha256:d0682897ed73ea71b4e5887fe310fc92d4774e8ccce4c3c7c16a5b49ca71c570
reactos-clang-cl-i386-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
146 MB
sha256:1f9848d1e9e6c5157a24b497a56693af7b6969c34e700bf4c4b3de725ff8cafd
reactos-clang-cl-i386-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
133 MB
sha256:07b5f85668a658990bafdd56eacb591d8003e75958594d3a84829bc05bc54214
reactos-clang-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
220 MB
sha256:1043f078a1a3d44c3b2a7d0cc9801f0dfa30d0682a94cf59c7bd80d19664286a
reactos-clang-i386-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
173 MB
sha256:9d79dd307442356f70285d373c85a9abfe612521502f7224a21ca1c9d4f16f29
reactos-gcc-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
438 MB
sha256:cb74dc06e98e31f64d7e89cc493c382f0484feae5e71d1890e37aaaf9e6d39ea
reactos-gcc-amd64-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
439 MB
sha256:7961d1a65b878b5ddbf850c19f3bf0a095b417b3b8e1b866488e7bc6bbac13c3
reactos-gcc-amd64-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
177 MB
sha256:b528838bb76c19f8cf586313cf0f46e039b902dbfbae605e7f98da4f3ad87ae3
reactos-gcc-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
210 MB
sha256:116959467ff0c1d877712c561b8872626cdb1cb80a5c8415f13004fd56b185ff
reactos-gcc-i386-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
211 MB
sha256:0c80c53fe609d4861cc5425fb5039f53801563678814496445295f61b999a108
reactos-gcc-i386-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
193 MB
sha256:52068a872111c1d3f398340b6ed9d469ce745860dfdb804b0642ed9ee7582e94
reactos-msvc14-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
151 MB
sha256:8fcf55550e3390d53fc1a68dcab65fdcd9bd3e22eb1ed9567c1f1b44771ad1f7
reactos-msvc14-amd64-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
151 MB
sha256:497e657453324fcd5b300f186ccef4c4f3b7eb1542c1d76dd1bcbc0f3135b394
reactos-msvc14-amd64-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
142 MB
sha256:c1d45813b83e15bd027378313b576a2d9935089bc8c906564b657af4e56a29d3
reactos-msvc14-arm-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
12.7 MB
sha256:493217c96c23fac0e12b6696b0b40d2321cddebeeab121bb5fd8df2d8ba799d5
reactos-msvc14-arm-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
10.8 MB
sha256:8bc26342c5f279d68c12d202ab230cb1bd3ec93d359c01c0c4fa31c155ee7585
reactos-msvc14-arm64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
3.21 MB
sha256:146f6b5edc8f38dba9594b2950b16bc3ddd7cb027b352112bbc7b535ef654531
reactos-msvc14-arm64-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
3.09 MB
sha256:85eaae78ce89f4f6dbd6b3a424702d842a2ca025d784c4ebd99c177422eb8bfa
reactos-msvc14-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
155 MB
sha256:7e6d047f7932cc977c07e828cac3ce02a9799736fb4bd7e11af60dbb0c6d8cf4
reactos-msvc14-i386-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
155 MB
sha256:2d3f0e2e5e0b23bd5cd44cfaaed26e41036eeeac8dabcdf69b92cab0e8bbd188
reactos-msvc14-i386-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
133 MB
sha256:3fc7270bcd2f9eaedb9960990180513ada6974ad35154065882835dc87d64c1b
reactos-msvc14.2-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
150 MB
sha256:6e9c9116bf3531e22e112c1cd04dca3cd77313d7b5d552e64c9aefd5ba7e2862
reactos-msvc14.2-amd64-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
142 MB
sha256:e60b14d876a27a7681cb8e08777ee81a2c4a97996bec9f4b94125ffd52c3d658
reactos-msvc14.2-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
155 MB
sha256:a48fa7245fac12ede31189efac05832581e91c5a02610f64cf99ee1d857aec1e
reactos-msvc14.2-i386-Release-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
133 MB
sha256:1be1f49f5550263d870c64c3d9c8b5f6b4fa50d4fc805ba1fe78b744a1a8cb34
reactos-msvc14.29-arm-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
12.7 MB
sha256:eaa8031111d35b87d15ef1ee34bc7d294bf19dbb6d6d6d33f79c05f815ce937a
reactos-msvc14.29-arm-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
10.8 MB
sha256:4d6ba769ccd507d837d073d422fcdbea355a2dfe59221473c31faa87d908da7e
reactos-msvc14.29-arm64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
3.2 MB
sha256:a0c3f15de4ba09e36b8abc6f93dd5240ba28795edc678c1999f4c160d9a942e7
reactos-msvc14.29-arm64-Release-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
3.07 MB
sha256:4bc5a9b001bd8e0468b34aa81998d5667565d2276710158c60862c3c572d2ccb
reactos-syms-clang-cl-amd64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
104 MB
sha256:717fe374be0ccebcd3148158626fa23db91def27d56222cc8e96a387b7a764d8
reactos-syms-clang-cl-i386-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
113 MB
sha256:87c12b41d4415ea3a800fe7e50ba235b4a2d777aafe5d975a503ce6819100594
reactos-syms-msvc14-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
228 MB
sha256:1472a07a5922e44921e0ea94cfb7dcf1157cde168c3cdaaa079cae7c0a3fefe2
reactos-syms-msvc14-amd64-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
228 MB
sha256:faed40041cc199ca9658af941413892bda2bb0cc39b824bb7b8add1c544ff20f
reactos-syms-msvc14-arm-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
54.6 MB
sha256:09e00b64d7996f884929bddb60f7e03d795746567b8936c8721c2224517a82ab
reactos-syms-msvc14-arm64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
7.81 MB
sha256:1a66aaa11eb64af60c79df8f254ff37d78c935a22b146123fbfecda2f68d73f5
reactos-syms-msvc14-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
235 MB
sha256:5834cf3d02674f8dfe6858e63c6248d91eaa74a4e0e23e0f98fa3a5db79e3379
reactos-syms-msvc14-i386-Debug-0x600-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
236 MB
sha256:da96ebead735140f247b37e4306626b5e1de6536a79bfb7a9f23ce7900ef8f5d
reactos-syms-msvc14.2-amd64-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
213 MB
sha256:d81d0a9266e6409f704704374addcf2f16b4901dcec1f5cb1efd78016b082e64
reactos-syms-msvc14.2-i386-Debug-0x502-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
219 MB
sha256:5c0f3c2fdf9724d2247c51fa4191e72c81671b5df6474378fb84d3e4cbca52b5
reactos-syms-msvc14.29-arm-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
50.3 MB
sha256:903136d81e031bf40742f2ad41c22e4a4942a5e9a053f2faa4f85e43d0ca919d
reactos-syms-msvc14.29-arm64-Debug-dcf822dfc9b180602bfdf7ac3f34c9adbac4589b
7.4 MB
sha256:18c5183b5c4c0f9f265ba883a3ace4edca4b8256d022c0ba044345bbf76c7aba