Skip to content

chore: bump deps to fix vulns #201

chore: bump deps to fix vulns

chore: bump deps to fix vulns #201

Triggered via pull request March 25, 2026 02:36
Status Failure
Total duration 1m 55s
Artifacts 4

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

1 error, 9 warnings, and 1 notice
build (24)
Process completed with exit code 1.
scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1, anchore/sbom-action@55dc4ee22412511ee8c3142cbea40418e6cec693, anchore/scan-action/download-grype@64a33b277ea7a1215a3c142735a1091341939ff5, anchore/scan-action@64a33b277ea7a1215a3c142735a1091341939ff5, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
scan
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
scan
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
scan
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
build (24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
scan
Grype DB is updated succesfully

Artifacts

Produced during runtime
Name Size Digest
cve-report.json Expired
146 Bytes
sha256:1d5774bda000e8588ca1f475daf6f8a450e8bdacebc9c99b089c5b7cff9136c8
cve-report.sarif Expired
148 Bytes
sha256:a05a9bdb4be87f9342517fda9819b9c41a8756bcf77e5e64d0a20efbd26201d3
sbom.cyclonedx.json Expired
5.15 KB
sha256:f165f3c2f742224855de68be8fe59dd4576d4d2b61f3777e7bcb6c01c846f151
sbom.spdx.json Expired
7.57 KB
sha256:3ae98c257ced0700b46eeab1fe16e2afd7eab46d0bc1a3d443f09fd078a2e1fb