Skip to content

Adds possibility to define a specific dapr cli version (#228) #118

Adds possibility to define a specific dapr cli version (#228)

Adds possibility to define a specific dapr cli version (#228) #118

Triggered via push July 18, 2024 10:44
Status Failure
Total duration 19s
Artifacts

dapr-deploy.yml

on: push
update dapr runtime on release longhaul cluster
10s
update dapr runtime on release longhaul cluster
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
update dapr runtime on release longhaul cluster
Process completed with exit code 1.
update dapr runtime on release longhaul cluster
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/setup-helm@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
update dapr runtime on release longhaul cluster
The following actions uses Node.js version which is deprecated and will be forced to run on node20: azure/setup-helm@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
update dapr runtime on release longhaul cluster
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/