Skip to content

Bump dompurify from 3.2.7 to 3.4.0 #254

Bump dompurify from 3.2.7 to 3.4.0

Bump dompurify from 3.2.7 to 3.4.0 #254

Triggered via pull request April 16, 2026 03:29
Status Success
Total duration 59s
Artifacts 3

pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
6s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
9s
Commit stage / Check English usage
Commit stage  /  Count lines of code
5s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
47s
Commit stage / Scan dependencies
Commit stage  /  Lint and validate OpenAPI
43s
Commit stage / Lint and validate OpenAPI
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
Commit stage / Lint and validate OpenAPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@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/
Commit stage / Lint and validate OpenAPI: build/specification/sandbox/eligibility-signposting-api.yaml#L22
operation-tags Operation must have non-empty "tags" array.
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip
814 Bytes
sha256:cac185d7ce77214eaea9e5442bb9284933126c12c253df73fba5ae0294f221c2
sbom-repository-report.json.zip
79 KB
sha256:783dd403b16f00151fb0072833ac68751a9c2265f9f3013b8533bc70f9f08aa5
vulnerabilities-repository-report.json.zip
12.2 KB
sha256:2f1731cd10ad34bea58e57c3e4446d29e62153a5af3819d32c62b88dfaa72a61