Skip to content

Bump dompurify from 3.2.7 to 3.3.3 #191

Bump dompurify from 3.2.7 to 3.3.3

Bump dompurify from 3.2.7 to 3.3.3 #191

Triggered via pull request March 28, 2026 10:28
Status Success
Total duration 1m 5s
Artifacts 3

pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
6s
Commit stage / Check English usage
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
44s
Commit stage / Scan dependencies
Commit stage  /  Lint and validate OpenAPI
40s
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 Expired
814 Bytes
sha256:5352da981e5da367e6aeaf8fa6df69eb78ea6631fffcc7c952193299b9532259
sbom-repository-report.json.zip Expired
78.6 KB
sha256:291f7c9ce421865b939cf65e0ddeb2c08cedbc8b5d662d43e0741ac7de6a63f8
vulnerabilities-repository-report.json.zip Expired
20.6 KB
sha256:2ea9bfe88da0969b67347ff5c556522d43387483b814b078d2ce96234352d4fc