Skip to content

feat(workflow): add PE upgrade step with legacy compilers #5

feat(workflow): add PE upgrade step with legacy compilers

feat(workflow): add PE upgrade step with legacy compilers #5

Triggered via push September 24, 2024 14:14
Status Failure
Total duration 58m 46s
Artifacts
Convert compilers to legacy
58m 37s
Convert compilers to legacy
Install and Upgrade PE with legacy compilers
24m 44s
Install and Upgrade PE with legacy compilers
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Install and Upgrade PE with legacy compilers
Process completed with exit code 1.
Convert compilers to legacy
Process completed with exit code 1.
Install and Upgrade PE with legacy compilers
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/
Install and Upgrade PE with legacy compilers
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/
Convert compilers to legacy
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/
Convert compilers to legacy
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/