Bump jinja2 from 3.1.2 to 3.1.3 #8138
Triggered via pull request
January 11, 2024 04:00
Satellite-QE
closed
#13729
Status
Failure
Total duration
41s
Artifacts
–
auto_cherry_pick.yml
on: pull_request_target
Find & Save last PRT comment of Parent PR
3s
Matrix: Auto Cherry Pick to labeled branches
Annotations
5 errors and 4 warnings
Auto Cherry Pick to labeled branches (6.12.z)
Either "filePath" or "message" should be provided as input
|
Auto Cherry Pick to labeled branches (6.13.z)
Either "filePath" or "message" should be provided as input
|
Auto Cherry Pick to labeled branches (6.15.z)
Either "filePath" or "message" should be provided as input
|
Auto Cherry Pick to labeled branches (6.14.z)
The job was canceled because "_6_12_z" failed.
|
Auto Cherry Pick to labeled branches (6.14.z)
Either "filePath" or "message" should be provided as input
|
Auto Cherry Pick to labeled branches (6.12.z)
The following actions uses node12 which is deprecated and will be forced to run on node16: jyejare/github-cherry-pick-action@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Auto Cherry Pick to labeled branches (6.13.z)
The following actions uses node12 which is deprecated and will be forced to run on node16: jyejare/github-cherry-pick-action@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Auto Cherry Pick to labeled branches (6.15.z)
The following actions uses node12 which is deprecated and will be forced to run on node16: jyejare/github-cherry-pick-action@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Auto Cherry Pick to labeled branches (6.14.z)
The following actions uses node12 which is deprecated and will be forced to run on node16: jyejare/github-cherry-pick-action@main. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|