Skip to content

[RAPPS] Fix loading of default settings (#8715) #103

[RAPPS] Fix loading of default settings (#8715)

[RAPPS] Fix loading of default settings (#8715) #103

Triggered via push March 17, 2026 15:13
Status Success
Total duration 30m 24s
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.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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
463 MB
sha256:4fc03a519c7164e58dcc427391978d57c688112e7a04591e37e7f8f0bfc039da
reactos-clang-amd64-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
175 MB
sha256:9fd450580702c2b7e6028f4cb3137fd6cb7dd4c13a568fca71a64db6fe4c465c
reactos-clang-cl-amd64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
145 MB
sha256:3578f780c08e8b0303499e7806b3f1c928eb40270f0b8b5ff1cc1e3d95366ac3
reactos-clang-cl-amd64-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
134 MB
sha256:d7fde8b710078e9d9bacc33a044868a8d92ed84f049a588ea5380a22929b59ee
reactos-clang-cl-i386-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
147 MB
sha256:cc4b3ca6c94f70ec777737a63bda19b76ca377fa2ca51fb493498924d378896a
reactos-clang-cl-i386-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
134 MB
sha256:eb00dab60ce88adfcfde19e32de66665f3940575e704d93e167823fb786233bd
reactos-clang-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
217 MB
sha256:408c2365be41cfa0d4f39f477661eea8f6a2569c31e3bd26c791175e84d3fb26
reactos-clang-i386-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
174 MB
sha256:7b1abbbde3ae678a3fe3e43e4dfe246e610edd4c99cd7ee17a4625ba09fd3ebc
reactos-gcc-amd64-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
431 MB
sha256:0bc5accbe86fc3da9cb4961b8c1684e6f1a1c06e41883c450046ec2db1d781aa
reactos-gcc-amd64-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
432 MB
sha256:ee300035e496a8de71632a8a98188484a69536bbd51c4e51d4db3465e5e2ed58
reactos-gcc-amd64-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
178 MB
sha256:cedbd1752bb043e5d8a18d45cd7dec394be12453a87d04cb41654265f699f1f1
reactos-gcc-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
208 MB
sha256:2848b86479020883038453f79fc8ae46044d1a91870e4efe79e3db1b03614393
reactos-gcc-i386-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
209 MB
sha256:f1700407c714df09f48adf280c2d9502524c9f3876568d82f1d0a0225d40f00d
reactos-gcc-i386-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
194 MB
sha256:688ce0b368b9af89de966ebb824630c4f28e300ccd187e497a2e950db3c5fa0e
reactos-msvc14-amd64-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
152 MB
sha256:dc8a3c61188a64a2a1b6cf0e323abc517f69a8957c34a30348e94ba8862ada9c
reactos-msvc14-amd64-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
152 MB
sha256:78057fe08bc7ed1568c27502632db9cd3ca762af1c0c086d40137b2449b193c1
reactos-msvc14-amd64-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
140 MB
sha256:0203dfc0690290c06f57d82a218a6f8fb2a8aa4bd64bdb3dcb5cdcf780b4b918
reactos-msvc14-arm-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
12.7 MB
sha256:36c3b6ea8534804e9dc2896a3700d7373f85550c2806b5513bb19aae83f10381
reactos-msvc14-arm-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
10.8 MB
sha256:9a212a93e3b8267c0664000157690e0c4ffacf1e2fe454fb09d2b72d79ae4ee1
reactos-msvc14-arm64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
3.2 MB
sha256:1091a50dfc972cf51781ae956ff12828e190b264629e612064a62fc9ab2058a3
reactos-msvc14-arm64-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
3.09 MB
sha256:e99f7423b2d0ebcac5f89c31df9b25dc15637bcd318aa24f296ad899b53dc041
reactos-msvc14-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
156 MB
sha256:d60eb9f2b675c39ea28efd48fe8615fd37bf94d402853aa8d8e7bd017d75c684
reactos-msvc14-i386-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
156 MB
sha256:4eb7f47c677a6ec6c8af5c622bfe67d8aed94eb2b0c3bdb2aca64f465af75ed3
reactos-msvc14-i386-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
132 MB
sha256:097015ad471985d95b034b1e960e6f59fd357f12111ca86a6c4c28e97d197027
reactos-msvc14.2-amd64-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
151 MB
sha256:a0a712fa8800632873026840f2f92f64d2348dfb46e780515724689d66bec0e5
reactos-msvc14.2-amd64-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
140 MB
sha256:a405a4faf698386003c30cc28a6f8bbef67156417d616fa44791220cb1d4aed8
reactos-msvc14.2-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
156 MB
sha256:8a668a17deb954f8ef5921ca328b36992807cc6046dafba8bf08ca4097c9c601
reactos-msvc14.2-i386-Release-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
132 MB
sha256:5e21bd1b3b31fac92503b222c090ddf56b774950a8e002a2a03d1c1adf52547d
reactos-msvc14.29-arm-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
12.7 MB
sha256:3e43352a5f5db98b9ac31532950aedf1be36a6cbceca3c09b87274c68f37b851
reactos-msvc14.29-arm-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
10.7 MB
sha256:f63fa0283680aaf34bbcef1ef9ffc4ff5e7fbb19aae63215b86bac8ff146880c
reactos-msvc14.29-arm64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
3.2 MB
sha256:95aa34e2c38ee5c9f0c89331f9a3174a592775696848790b302658c797cfcb31
reactos-msvc14.29-arm64-Release-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
3.07 MB
sha256:0fe349912eae30a0d055366823801d5c8540976632216c05bdfa5542cc12c43f
reactos-syms-clang-cl-amd64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
103 MB
sha256:f13c797e5ae515a25f866d4759e4d81a773720589f074bc83868d1905c8f78df
reactos-syms-clang-cl-i386-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
112 MB
sha256:38cd45f3a9d0291a3afe95e153bcc813e38313a6cd367e0dd9db08076a24a8d5
reactos-syms-msvc14-amd64-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
226 MB
sha256:b8efa108b326c207305137125a2f04e66918cd9e2085b88beb85c39d2b68d177
reactos-syms-msvc14-amd64-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
226 MB
sha256:66ecc42c62af27972c99beaf97a8145838d8b2d5b02d392f2f9a5989385f358b
reactos-syms-msvc14-arm-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
54.7 MB
sha256:edd60a73a9e8a1ea5b4664f8d070c5317920b2a9806574c37564892497624c22
reactos-syms-msvc14-arm64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
7.73 MB
sha256:3a12e9f27704817fa8dc8eede04104e984da00cc326bef470b4a84708e9256af
reactos-syms-msvc14-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
233 MB
sha256:23f3377fc285cfc8b54d90cd4811cbb5979de7c6b21bc025a9b534a73b0e0b54
reactos-syms-msvc14-i386-Debug-0x600-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
233 MB
sha256:084dcb42257586e56f92c99be6f0879004b0f15f32c76776b6f2770f2b802530
reactos-syms-msvc14.2-amd64-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
211 MB
sha256:a38a35a311a857bafcd2f1ec8bf55be8926b4765f36cb8277206edcd5117b955
reactos-syms-msvc14.2-i386-Debug-0x502-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
217 MB
sha256:f672d567ff040d2cc44d8bd700eda3a52f5c5bfd5183957e8ee5a26ea3b76ad3
reactos-syms-msvc14.29-arm-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
50.4 MB
sha256:6caf5d40d2c4c14aaef64bed0e3d86d44bcb503f433b8ae689afeb0c0ec9324c
reactos-syms-msvc14.29-arm64-Debug-b3ff1ff98fdfeb58b3e80b0c123979fede80b358
7.32 MB
sha256:37805e3e3002e6da3148b3ccaabbd405ac4e3975605ee1dec3d2fa135324aea9