Skip to content
CI

Automatic catch up from 5.4 to 5.11 #401

Sign in to view logs

Automatic catch up from 5.4 to 5.11

Automatic catch up from 5.4 to 5.11 #401

Triggered via pull request October 4, 2024 09:40
@BlueCutOfficialBlueCutOfficial
synchronize #276
catchup-5.11
Status Success
Total duration 56s
Artifacts –

ci.yml

on: pull_request
Lint files
44s
Lint files
Test node-tests
35s
Test node-tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test node-tests
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/
Test node-tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Lint files
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/
Lint files
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/