Skip to content

Bump picomatch from 2.3.1 to 2.3.2 #224

Bump picomatch from 2.3.1 to 2.3.2

Bump picomatch from 2.3.1 to 2.3.2 #224

Triggered via pull request April 10, 2026 08:57
Status Success
Total duration 1m 1s
Artifacts 3

pull-request.yaml

on: pull_request
Set CI/CD metadata
3s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
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
10s
Commit stage / Check English usage
Commit stage  /  Count lines of code
5s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
50s
Commit stage / Scan dependencies
Commit stage  /  Lint and validate OpenAPI
35s
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
813 Bytes
sha256:bf8ab26cffa26f4847615ec1990a103a7ef34f83ca69d495311b0c41859b6ccc
sbom-repository-report.json.zip Expired
78.7 KB
sha256:b277dfabcaf47d7b5810ceb505fda7f68802db21777a8a60b5f9ac09e1925e3b
vulnerabilities-repository-report.json.zip Expired
16.8 KB
sha256:e3a2f29964b7a074738fc4e25f27f0720c8809a2052da053db727029db296202