Skip to content

chore(deps): bump elliptic from 6.5.7 to 6.6.0 (#11708) #5256

chore(deps): bump elliptic from 6.5.7 to 6.6.0 (#11708)

chore(deps): bump elliptic from 6.5.7 to 6.6.0 (#11708) #5256

Triggered via push November 1, 2024 15:33
Status Success
Total duration 12m 54s
Artifacts
🦜 Publish Canary
12m 25s
🦜 Publish Canary
πŸ’¬ Message Slack
11s
πŸ’¬ 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.