Skip to content

chore: run yaml linter only on assets #214

chore: run yaml linter only on assets

chore: run yaml linter only on assets #214

Triggered via push October 27, 2023 23:25
Status Success
Total duration 3m 36s
Artifacts

cicd.yml

on: push
Matrix: run-js-tests
run-linter
9s
run-linter
publish-js-package
0s
publish-js-package
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
run-linter
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run-js-tests (14.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/
run-js-tests (12.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/
run-js-tests (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/