fix(auth): using theme color instead of hardcoded value #12
Triggered via issue
October 15, 2024 08:29
Status
Success
Total duration
11s
Artifacts
–
issue-labels.yml
on: issue_comment
label-op-response
2s
label-new-issue
2s
Annotations
1 error and 5 warnings
label-op-response
Error: failed to remove labels: blocked: customer-response
|
label-new-issue
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-add-labels@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
label-new-issue
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-add-labels@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
label-op-response
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-add-labels@v1, actions-ecosystem/action-remove-labels@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
label-op-response
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-add-labels@v1, actions-ecosystem/action-remove-labels@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
label-op-response
failed to remove label: blocked: customer-response: HttpError: Label does not exist
|