Skip to content

fix: address PR #101 review comments #212

fix: address PR #101 review comments

fix: address PR #101 review comments #212

Triggered via push April 10, 2026 04:59
Status Success
Total duration 11m 26s
Artifacts 11

CI_build.yml

on: push
before_build
32s
before_build
Matrix: build_windows
Matrix: build_windows_cmake
Matrix: build_windows_msys2
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
before_build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_windows (Debug, ARM64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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_windows (Release, Win32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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_windows_cmake (Release, x64, amd64)
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, microsoft/setup-msbuild@v2. 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_windows (Release, x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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_windows (Release, ARM64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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_windows (Debug, Win32)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, microsoft/setup-msbuild@v2. 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_windows (Debug, x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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
Notepad++.MSVC.ARM64.Debug
5.99 MB
sha256:e28cb489c036219c8e150e6dcf475e975e2116ebde03993bcbe1b8b7227630fd
Notepad++.MSVC.ARM64.Release
4.52 MB
sha256:c86975accbe6163f5e9c354c1e5b218e5b70edf4085a48139afe4f8da635eed4
Notepad++.MSVC.Win32.Debug
5.74 MB
sha256:b2cfcc8d551044e2777b96ed510c2164c56df558bd89d1a8cbd5b24f31312304
Notepad++.MSVC.Win32.Release
4.22 MB
sha256:81d8b2ea4af2503fbf7c127ac3acc70df8925dcb6d2f19e737728aa5a61b54c9
Notepad++.MSVC.x64.Debug
6.14 MB
sha256:ac19f6beb5b6855f8f9d5b5729fe9b9b8aad01f2c0829f23e2a8930833b3d47f
Notepad++.MSVC.x64.Release
4.53 MB
sha256:6f6a9bb77c2a54abdea617422296c80c0b33883142ff9ba0017d32bbba74c144
Notepad++.clang.x86_64.Release
5.12 MB
sha256:10a27d74bc40592c7715541079652371d55e105fdfb8d5f58cbd726e30e8d593
Notepad++.gcc.i686.Debug
31.7 MB
sha256:b468d20d7c209f5173a6b7e063e4ea9890ab16aadeb18bd2f9deaa642dfa8b32
Notepad++.gcc.i686.Release
6.24 MB
sha256:cf0a548019541f6547421f1e6d8c1f4b3b0b622bb5e57529a0389b8a1a11fb5c
Notepad++.gcc.x86_64.Debug
32.9 MB
sha256:63869303ffaa9e95fb806c6ae756ab9f49c85cf6349563c067b4b6f81c8f7c4c
Notepad++.gcc.x86_64.Release
6.14 MB
sha256:e5c9c4664bc6ab1cecf8b06eed9563daa629554a4514997d2dab48e49c2a0d14