Skip to content

Get Node versions #1431

Get Node versions

Get Node versions #1431

Triggered via schedule October 4, 2024 03:20
Status Failure
Total duration 1m 45s
Artifacts

get-node-versions.yml

on: schedule
get-new-node-versions  /  Find new versions
11s
get-new-node-versions / Find new versions
get-new-node-versions  /  Check new versions
7s
get-new-node-versions / Check new versions
get-new-node-versions  /  Trigger builds
0s
get-new-node-versions / Trigger builds
get-new-node-versions  /  Check build for failures
13s
get-new-node-versions / Check build for failures
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
get-new-node-versions / Check new versions
Process completed with exit code 1.
get-new-node-versions / Check build for failures
Process completed with exit code 1.
get-new-node-versions / Find new versions
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
get-new-node-versions / Check new versions
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
get-new-node-versions / Check build for failures
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/