Skip to content

Merge pull request #4 from rustsbi/dependabot/cargo/rustix-0.36.16 #37

Merge pull request #4 from rustsbi/dependabot/cargo/rustix-0.36.16

Merge pull request #4 from rustsbi/dependabot/cargo/rustix-0.36.16 #37

Triggered via push October 21, 2023 03:25
Status Success
Total duration 2m 45s
Artifacts

workflow.yml

on: push
Run rust-clippy analyzing
2m 36s
Run rust-clippy analyzing
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
Run rust-clippy analyzing
could not compile `proc-macro2` (lib) due to 2 previous errors
Run rust-clippy analyzing
unknown feature `proc_macro_span_shrink`
Run rust-clippy analyzing
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1, actions-rs/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run rust-clippy analyzing
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/
Run rust-clippy analyzing
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/
Run rust-clippy analyzing
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/
Run rust-clippy analyzing
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/
Run rust-clippy analyzing
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`