Skip to content

chore(deps): update babel monorepo to v7.25.7 (#11682) #5242

chore(deps): update babel monorepo to v7.25.7 (#11682)

chore(deps): update babel monorepo to v7.25.7 (#11682) #5242

Triggered via push October 8, 2024 00:03
Status Success
Total duration 8m 14s
Artifacts
🦜 Publish Canary
7m 52s
🦜 Publish Canary
πŸ’¬ Message Slack
6s
πŸ’¬ 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.