Skip to content

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

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

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

Triggered via push August 28, 2024 03:48
Status Failure
Total duration 30s
Artifacts

nodejs.yml

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

Annotations

2 errors and 4 warnings
build (10.x)
Process completed with exit code 1.
build (12.x)
Process completed with exit code 1.
build (10.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, 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 (10.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v1, 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 (12.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, 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/cache@v1, 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/