Skip to content

fix(scanner, manifest, build): one answer per question, and no key that reaches no decision (2026.9.9.1) #2071

fix(scanner, manifest, build): one answer per question, and no key that reaches no decision (2026.9.9.1)

fix(scanner, manifest, build): one answer per question, and no key that reaches no decision (2026.9.9.1) #2071

Triggered via pull request September 9, 2026 09:52
Status Success
Total duration 19m 3s
Artifacts 1

ci-windows.yml

on: pull_request
build + test + package (windows x64, self-host)
11m 29s
build + test + package (windows x64, self-host)
toolchains + regressions (windows x64)
14m 59s
toolchains + regressions (windows x64)
bare Windows: no Visual Studio (windows x64)
2m 58s
bare Windows: no Visual Studio (windows x64)
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build + test + package (windows x64, self-host)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
toolchains + regressions (windows x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
bare Windows: no Visual Studio (windows x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4. 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
mcpp-windows-x86_64
5.63 MB
sha256:780b9a77bdef868b457cda94cf44fe1a66a042d4cab74d3168fa57681d00486b