Skip to content

chore(vite): Refactor vite plugin - early return (#11727) #5268

chore(vite): Refactor vite plugin - early return (#11727)

chore(vite): Refactor vite plugin - early return (#11727) #5268

Triggered via push November 20, 2024 11:10
Status Success
Total duration 8m 53s
Artifacts
🦜 Publish Canary
8m 30s
🦜 Publish Canary
πŸ’¬ Message Slack
8s
πŸ’¬ 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.