Skip to content

fix: package.json & package-lock.json to reduce vulnerabilities #196

fix: package.json & package-lock.json to reduce vulnerabilities

fix: package.json & package-lock.json to reduce vulnerabilities #196

Triggered via push September 18, 2024 06:29
Status Failure
Total duration 58s
Artifacts

nodejs.yml

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

Annotations

4 errors and 4 warnings
build (12.x)
Process completed with exit code 1.
build (14.x)
Process completed with exit code 1.
build (10.x)
The job was canceled because "_12_x" failed.
build (10.x)
The operation was canceled.
build (12.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (12.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (14.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (14.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/