Skip to content

chore: use self references in type tests (#11716) #5257

chore: use self references in type tests (#11716)

chore: use self references in type tests (#11716) #5257

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