Skip to content

fix(jobs): merge job options to prevent 'undefined' values in place o… #5226

fix(jobs): merge job options to prevent 'undefined' values in place o…

fix(jobs): merge job options to prevent 'undefined' values in place o… #5226

Triggered via push October 7, 2024 21:21
Status Success
Total duration 8m 38s
Artifacts
🦜 Publish Canary
8m 14s
🦜 Publish Canary
💬 Message Slack
7s
💬 Message Slack
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
🦜 Publish Canary
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.