Skip to content

Blog: add post about HashDoS fix in Mar 2026 security release #8924

Blog: add post about HashDoS fix in Mar 2026 security release

Blog: add post about HashDoS fix in Mar 2026 security release #8924

Triggered via pull request March 24, 2026 23:02
Status Cancelled
Total duration 3m 22s
Artifacts 1

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Build on windows-latest
Canceling since a higher priority waiting request for Build-refs/pull/8777/merge exists
Build on windows-latest
The operation was canceled.
Build
Canceling since a higher priority waiting request for Build-refs/pull/8777/merge exists
Build on ubuntu-latest
Canceling since a higher priority waiting request for Build-refs/pull/8777/merge exists
Build on ubuntu-latest
The operation was canceled.
Build on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda, step-security/harden-runner@f4a75cfd619ee5ce8d5b864b0d183aff3c69b55a. 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 on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda, step-security/harden-runner@f4a75cfd619ee5ce8d5b864b0d183aff3c69b55a. 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
webpack-stats
54.8 KB
sha256:35690639489d8b04870a43139ca4ba630ebd53428c51fba7e5cd9030c22e2a44