Skip to content

DisruptionCrons should not halt if they've missed 100 starts (#904) #212

DisruptionCrons should not halt if they've missed 100 starts (#904)

DisruptionCrons should not halt if they've missed 100 starts (#904) #212

Triggered via push September 6, 2024 16:59
Status Success
Total duration 7m 16s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
goreleaser
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
goreleaser
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
goreleaser
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/