Skip to content

fix: avoid leaving canisters in stopped state if an upgrade fails (#439) #59

fix: avoid leaving canisters in stopped state if an upgrade fails (#439)

fix: avoid leaving canisters in stopped state if an upgrade fails (#439) #59

Re-run triggered October 30, 2024 07:53
Status Success
Total duration 36m 40s
Artifacts
Publish canister artifacts and send upgrade proposals
15m 55s
Publish canister artifacts and send upgrade proposals
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Publish canister artifacts and send upgrade proposals
The following actions uses node12 which is deprecated and will be forced to run on node16: marvinpinto/action-automatic-releases@latest. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Publish canister artifacts and send upgrade proposals
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, marvinpinto/action-automatic-releases@latest. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish canister artifacts and send upgrade proposals
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/
Publish canister artifacts and send upgrade proposals
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/