Skip to content

[SDK][IMM32][NTUSER] Delete <jpnvkeys.h> and use <wine/ime.h> instead… #115

[SDK][IMM32][NTUSER] Delete <jpnvkeys.h> and use <wine/ime.h> instead…

[SDK][IMM32][NTUSER] Delete <jpnvkeys.h> and use <wine/ime.h> instead… #115

Triggered via push April 10, 2026 02:17
Status Success
Total duration 47m 50s
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. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-msvc-arm (windows-latest, 14, arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-msvc-arm (windows-latest, 14.29, arm64, 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-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, 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, 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-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.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, 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, 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, amd64, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-msvc (windows-latest, 14.2, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-msvc (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 (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-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-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, 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, amd64, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-linux (clang, amd64, 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, 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, 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 (gcc, i386, Debug, 0x600)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-linux (gcc, i386, Release, 0x502)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-linux (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/

Artifacts

Produced during runtime
Name Size Digest
reactos-clang-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
471 MB
sha256:cc5e9a7cf934aea2fe918e7cd02a4fd03f9b6f1a8746a49b39c9fccc878e2fa2
reactos-clang-amd64-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
174 MB
sha256:9cae586ea754d1a211a43d84338313daf0d3dbea06f288564b5c805660604aa1
reactos-clang-cl-amd64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
144 MB
sha256:86c809201935ce60844d2822488d1a08c1ca546db353bee3b569e50482b8c5fe
reactos-clang-cl-amd64-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
133 MB
sha256:8cefe11ce7d7a29e636b26a9957e1eceff6711941aaf341836f7ea3ca07e4b04
reactos-clang-cl-i386-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
144 MB
sha256:e613ea5696285f97debdc9471aab9250037bdb1cf88be0071b398411b71191b2
reactos-clang-cl-i386-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
132 MB
sha256:e88fa8b22d3ee8dab7e9c9a7b4441911afd559f66c4b6b8883f8862bfb426294
reactos-clang-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
217 MB
sha256:09bd5c314bc71f814c0e842459f8109450f57f1f0a86ba793092bf0571b127a9
reactos-clang-i386-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
171 MB
sha256:94bcc26662dcbb4033bb9a4b2522517c9894c47513d0a54faca5b7b094519934
reactos-gcc-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
438 MB
sha256:71255d2085f0727741bda2a6950e5e53d8f69221c7c3ce15916b77134e7998ab
reactos-gcc-amd64-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
439 MB
sha256:64c4585a7435dbce6ffb31858058e2ee1c943a00d455fa5383153c37b372e0dd
reactos-gcc-amd64-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
177 MB
sha256:9e934708b20cd4a56e6839264ccec44f6fcaf984031a510d18e6c5683fcb63e6
reactos-gcc-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
208 MB
sha256:7e200566d9192e7b84091cb9c704fc568683b3cac7166941bb57d1313050bc20
reactos-gcc-i386-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
209 MB
sha256:11914de41a16bb875413942044beb6b89feebd91c93c0a54a662c1a7a269721e
reactos-gcc-i386-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
191 MB
sha256:5be3590fad9bbcad443eeae7762d0e0c048ec6d0b52eb4662d4b8d323ee2050d
reactos-msvc14-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
151 MB
sha256:6afb9c8244c6f8e69bc86f706d1c1b05144599d45ac72fc5767317fc66655fee
reactos-msvc14-amd64-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
151 MB
sha256:fe15a23ce2d91ccd9f5e65a200fe94286b65f9deeac22fe88fe36550fb4b644e
reactos-msvc14-amd64-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
142 MB
sha256:e177d90a4535178f2741136ccbb079679f7bfacd4bbc96afb87a455aea6a150b
reactos-msvc14-arm-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
12.7 MB
sha256:472f1ab8ab8a9c7d556e3f56f72c4bd6bb5af7e006bb3165d6017d0e65401db3
reactos-msvc14-arm-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
10.8 MB
sha256:0672f0c22b51da1cfd93540791c7669c2ae8886ddc87ece6d56110aa7f320ac0
reactos-msvc14-arm64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
3.21 MB
sha256:590a30ba26749fb6844abf035a76c196432d5b2afa60be9d570aaeca963ef496
reactos-msvc14-arm64-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
3.09 MB
sha256:c9b61e038877c6d067694d90a9782e96fcab6c79154f3287c6dd9db0207dbc67
reactos-msvc14-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
153 MB
sha256:40fd454765ca4fc50118731723d7251156f664c15675d28efbea57462ed95583
reactos-msvc14-i386-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
154 MB
sha256:7fd74aa7d6b4703e1cc01a16831d4327e9009420e2f0a7b9af5928716b72e951
reactos-msvc14-i386-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
132 MB
sha256:7b4db673a346b8e81f4a943c7555091c97995542a6bb8b2e1266b6bd7892b39c
reactos-msvc14.2-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
150 MB
sha256:cc04004e466eb321ca6c84dc32ca049d7e7d63b7bebcbe5d8439d6d37ccd6bbd
reactos-msvc14.2-amd64-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
142 MB
sha256:4b3def6fe062ccedf08fa5f9072114f08895ab1c4b4642c95994d23a6a10eb8f
reactos-msvc14.2-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
153 MB
sha256:5f23ddbf0807a5072b0207ea835f16fa7f70dd102885c9ee8201917d5293e805
reactos-msvc14.2-i386-Release-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
132 MB
sha256:0d85729b85b72057b84e46018ab85e85b8b33e51428bb8a6e435136204d56402
reactos-msvc14.29-arm-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
12.7 MB
sha256:ceb1af03825789dafc2d2ede347ef7bf4f76d0cba1ea3a505e6a7cb7ecccef74
reactos-msvc14.29-arm-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
10.8 MB
sha256:355ba2b49fb0b50bfef5c33d1587528ca7556b506d0bdb893857162917fa0547
reactos-msvc14.29-arm64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
3.2 MB
sha256:04545e79418508affac83cd0a2ad0558f1e98b4e007b1abeb7d7ceee36a45f7f
reactos-msvc14.29-arm64-Release-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
3.07 MB
sha256:282c8b9e9258efd0a1765aa276170f26f8a3d47922e9cc18c4bef7d6fb6919d6
reactos-syms-clang-cl-amd64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
104 MB
sha256:fd3432da2ee63c5345f39942fdd69538a61e966242b68b6392013884bbd8a6e9
reactos-syms-clang-cl-i386-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
112 MB
sha256:49e25e7ddcb8cbf0ae9e03d12b49d1790c7052e63bc20600040b2164c94af692
reactos-syms-msvc14-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
228 MB
sha256:c0d3240f3cec38ad56fe6a7ac63de034a5264e21d50f31fe1394f58832b26ad5
reactos-syms-msvc14-amd64-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
228 MB
sha256:a6a1e3049603aced1edf48924032a8ce524bccb589c9e4c0f6719eddd367e347
reactos-syms-msvc14-arm-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
54.6 MB
sha256:17d7f3e1821884a21fbb350cc9a022811f534a3372a5201ab20aa42a8ce35cb7
reactos-syms-msvc14-arm64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
7.85 MB
sha256:ee56b7bcc907023d35b5f5c0866e666bfb317a09e650dc80ecf42884bb7d0b34
reactos-syms-msvc14-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
233 MB
sha256:906dd0d54bba73fcafac53df4bd9d0c563def7a44d6748ba311f8ba9d4284a11
reactos-syms-msvc14-i386-Debug-0x600-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
234 MB
sha256:ed17565ad16f3ff09ac7b119b3aacafc599e48fed287ef6e5812cefa29d457f1
reactos-syms-msvc14.2-amd64-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
213 MB
sha256:521fa2047e3dab912ff434c75dc322c29a33904acce02458ac460e5a867fd68d
reactos-syms-msvc14.2-i386-Debug-0x502-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
217 MB
sha256:cc119293ae75b363e588030e91b77c6b93d62b8d3a0bd83ce6eb04c9962d380c
reactos-syms-msvc14.29-arm-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
50.3 MB
sha256:31cfb7f7a235f60cddf4eabd8461326f66a1b0d3e7b6ed9545975149fc63a583
reactos-syms-msvc14.29-arm64-Debug-61fb4db34c6cb8d97ab65feab8fb264e59079bc1
7.4 MB
sha256:1c69c81ea8c3c0715964d2dd0f4d310eaa46bb7ad5e191d54bd286d66f7f1312