Dev/env var #38
Annotations
2 errors and 11 warnings
The run was canceled by @joshrmcdaniel.
|
Run actions-rs/clippy-check@v1
The operation was canceled.
|
Build web frontend
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Build web frontend:
web_frontend/src/filterlists.rs#L2
unused imports: `save_button` and `submit_banner`
|
Build web frontend:
web_frontend/src/filterlists.rs#L100
type alias `FilterListSyntaxes` is never used
|
Build web frontend:
web_frontend/src/submit_banner.rs#L8
variant `Red` is never constructed
|
Build web frontend
`web_frontend` (bin "web_frontend") generated 3 warnings (run `cargo fix --bin "web_frontend"` to apply 1 suggestion)
|
Run actions-rs/toolchain@v1
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 actions-rs/toolchain@v1
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 actions-rs/toolchain@v1
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 actions-rs/toolchain@v1
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 actions-rs/clippy-check@v1
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Install trunk
package `libc v0.2.154` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
Loading