Skip to content

[Security Fix] Running a workflow when a pull request is assigned or labelled #569

[Security Fix] Running a workflow when a pull request is assigned or labelled

[Security Fix] Running a workflow when a pull request is assigned or labelled #569

Triggered via pull request September 18, 2024 06:50
Status Success
Total duration 39m 33s
Artifacts

unit-tests.yaml

on: pull_request
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build and test with torch-2.1
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 and test with torch-2.1
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. 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 with torch-1.14
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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 and test with torch-1.14
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/