Skip to content

Bump unsafe-libyaml from 0.2.8 to 0.2.10 (#434) #562

Bump unsafe-libyaml from 0.2.8 to 0.2.10 (#434)

Bump unsafe-libyaml from 0.2.8 to 0.2.10 (#434) #562

Triggered via push January 2, 2024 06:06
Status Success
Total duration 35m 8s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
acceptance-tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
acceptance-tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
acceptance-tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
acceptance-tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
acceptance-tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/