Skip to content

Bump picomatch from 2.3.1 to 2.3.2 #232

Bump picomatch from 2.3.1 to 2.3.2

Bump picomatch from 2.3.1 to 2.3.2 #232

Triggered via pull request April 10, 2026 09:09
Status Success
Total duration 53s
Artifacts 3

pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
9s
Commit stage / Scan secrets
Commit stage  /  Check file format
10s
Commit stage / Check file format
Commit stage  /  Check Markdown format
3s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
11s
Commit stage / Check English usage
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
41s
Commit stage / Scan dependencies
Commit stage  /  Lint and validate OpenAPI
41s
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 / 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/
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.

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip Expired
811 Bytes
sha256:dacd854b6a41d6c80dc992a20c792bd855c28eebc2910c79b1d715a20c45153b
sbom-repository-report.json.zip Expired
78.9 KB
sha256:78318d71bde3b28b485a2106d70fe8322bc32baa8aae924808044e7b62669e05
vulnerabilities-repository-report.json.zip Expired
11.9 KB
sha256:c9db4bbe746e07d00ca5f4298f7d99b80df0a0c931595d7ea8267cd216b44508