Skip to content

[Bug]: Windows 11 April 2026 LCU pushed out a new DBXUpdateSVN.bin file #41

[Bug]: Windows 11 April 2026 LCU pushed out a new DBXUpdateSVN.bin file

[Bug]: Windows 11 April 2026 LCU pushed out a new DBXUpdateSVN.bin file #41

Triggered via issue April 15, 2026 03:55
Status Success
Total duration 43m 6s
Artifacts

triage-issues.yml

on: issues
Matrix: triage / Triage Issues
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
triage / Triage Issues (feature_request.yml)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/advanced-issue-labeler@v2, stefanbuck/github-issue-parser@v3. 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/
triage / Triage Issues (feature_request.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
triage / Triage Issues (feature_request.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
triage / Triage Issues (bug_report.yml)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/advanced-issue-labeler@v2, stefanbuck/github-issue-parser@v3. 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/
triage / Triage Issues (bug_report.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
triage / Triage Issues (bug_report.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
triage / Triage Issues (documentation_request.yml)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: redhat-plumbers-in-action/advanced-issue-labeler@v2, stefanbuck/github-issue-parser@v3. 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/
triage / Triage Issues (documentation_request.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
triage / Triage Issues (documentation_request.yml)
Input 'app-id' has been deprecated with message: Use 'client-id' instead.