Skip to content

[BRE-139] - Revert to Using Push Trigger, Fix bug (#26) #14

[BRE-139] - Revert to Using Push Trigger, Fix bug (#26)

[BRE-139] - Revert to Using Push Trigger, Fix bug (#26) #14

Triggered via push November 6, 2024 15:03
Status Failure
Total duration 2m 3s
Artifacts

cd.yml

on: push
Get version type  /  Calculate Version
4s
Get version type / Calculate Version
Version bump
55s
Version bump
GitHub release
7s
GitHub release
Deploy workflow-linter (v2)
37s
Deploy workflow-linter (v2)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
GitHub release
Error 422: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
Version bump
The following actions use a deprecated Node.js version and will be forced to run on node20: Azure/login@e15b166166a8746d1a47596803bd8c1b595455cf, bitwarden/gh-actions/get-keyvault-secrets@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy workflow-linter (v2)
The following actions use a deprecated Node.js version and will be forced to run on node20: Azure/login@e15b166166a8746d1a47596803bd8c1b595455cf, bitwarden/gh-actions/get-keyvault-secrets@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/