Skip to content
Node CI

ci: Use GITHUB_OUTPUT envvar instead of set-output command #77

Sign in to view logs

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #77

Re-run triggered January 17, 2024 18:30
@manuelpuyolmanuelpuyol
#55
main
Status Success
Total duration 1m 47s
Artifacts –

nodejs.yml

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

Annotations

3 warnings
build (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/