Skip to content

Bump picomatch from 2.3.1 to 2.3.2 #251

Bump picomatch from 2.3.1 to 2.3.2

Bump picomatch from 2.3.1 to 2.3.2 #251

Triggered via pull request April 14, 2026 14:19
Status Success
Total duration 1m 0s
Artifacts 3

pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
9s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
Commit stage / Check English usage
Commit stage  /  Count lines of code
12s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
46s
Commit stage / Scan dependencies
Commit stage  /  Lint and validate OpenAPI
38s
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:21bb9db996196a9e9f2c991699ce4bcb53eeade731d19ca7db3a087febc5c487
sbom-repository-report.json.zip
78.9 KB
sha256:e0d80549f161e7f0564f8e8b0a1ab9ee4ad33ada5a48eb14d67e8ea163d8d029
vulnerabilities-repository-report.json.zip
12.4 KB
sha256:927ecd3845d772854c2a4a6a34fc8b7ce3a18f21b65ae5efe7060d93d33ca0ab