Skip to content

Release to Cargo

Release to Cargo #9

Triggered via push October 11, 2023 18:01
Status Failure
Total duration 7m 51s
Artifacts

rust_release.yml

on: push
Validate git tag
7s
Validate git tag
Release crate
2m 4s
Release crate
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 warnings
Release crate
failed to publish to registry at https://crates.io
Release crate
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
Validate git tag
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Release crate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Release crate
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/
Release crate
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/
Release crate
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/
Release crate
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/
Release crate
some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
Release crate
package `crossbeam-channel v0.5.6` in Cargo.lock is yanked in registry `crates-io`, consider updating to a version that is not yanked