Skip to content
CI

403 potential error-related comment (#1393) #1971

Sign in to view logs

403 potential error-related comment (#1393)

403 potential error-related comment (#1393) #1971

Triggered via push September 12, 2024 20:04
@riccardoferrettiriccardoferretti
pushed a8296c2
master
Status Success
Total duration 3m 19s
Artifacts –

ci.yml

on: push
Spell Check with Typos
6s
Spell Check with Typos
Lint
3m 9s
Lint
Build and Test
2m 12s
Build and Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Spell Check with Typos
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/
Build and Test
The following actions uses node12 which is deprecated and will be forced to run on node16: GabrielBB/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build and Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3, GabrielBB/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/