issue4083 change prefix meaning #6484
Triggered via pull request
November 22, 2024 14:44
pavelzlatnik
Status
Failure
Total duration
34m 29s
Artifacts
–
build-packaging.yml
on: pull_request
set-run-conditions
2s
check-permission
3s
display-dispatch-event-id
0s
call-integration-test
28m 13s
Annotations
1 error and 4 warnings
|
call-integration-test
Test workflow 5715 is not successful
|
|
regular-build
The following actions uses node12 which is deprecated and will be forced to run on node16: jfrog/setup-jfrog-cli@v2, actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
regular-build
The following actions use a deprecated Node.js version and will be forced to run on node20: jfrog/setup-jfrog-cli@v2, actions/github-script@v5, actions/[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/
|
|
call-integration-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
call-integration-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|