Skip to content

Add another critical extension bypass. (#501) #1035

Add another critical extension bypass. (#501)

Add another critical extension bypass. (#501) #1035

Triggered via push November 8, 2024 17:56
Status Success
Total duration 4m 37s
Artifacts

validations.yaml

on: push
Acceptance tests (Linux)
45s
Acceptance tests (Linux)
CLI tests
53s
CLI tests
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@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/
Unit tests
No files were found with the provided path: test/results/**/*. No artifacts will be uploaded.
Static analysis
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@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/
Build snapshot artifacts
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@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/
CLI tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@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/