chore: Bump clap from 3.2.25 to 4.5.19 #5241
Annotations
30 errors and 40 warnings
check:
cli/src/main.rs#L60
cannot find value `try_from_str` in this scope
|
check:
cli/src/main.rs#L64
cannot find value `try_from_str` in this scope
|
check:
cli/src/main.rs#L68
cannot find value `try_from_str` in this scope
|
check:
cli/src/main.rs#L72
cannot find value `try_from_str` in this scope
|
check:
cli/src/main.rs#L76
cannot find value `try_from_str` in this scope
|
check:
cli/src/main.rs#L60
no method named `parse` found for struct `Arg` in the current scope
|
check:
cli/src/main.rs#L64
no method named `parse` found for struct `Arg` in the current scope
|
check:
cli/src/main.rs#L68
no method named `parse` found for struct `Arg` in the current scope
|
check:
cli/src/main.rs#L72
no method named `parse` found for struct `Arg` in the current scope
|
check:
cli/src/main.rs#L76
no method named `parse` found for struct `Arg` in the current scope
|
test:
cli/src/main.rs#L60
cannot find value `try_from_str` in this scope
|
test:
cli/src/main.rs#L64
cannot find value `try_from_str` in this scope
|
test:
cli/src/main.rs#L68
cannot find value `try_from_str` in this scope
|
test:
cli/src/main.rs#L72
cannot find value `try_from_str` in this scope
|
test:
cli/src/main.rs#L76
cannot find value `try_from_str` in this scope
|
test:
cli/src/main.rs#L60
no method named `parse` found for struct `Arg` in the current scope
|
test:
cli/src/main.rs#L64
no method named `parse` found for struct `Arg` in the current scope
|
test:
cli/src/main.rs#L68
no method named `parse` found for struct `Arg` in the current scope
|
test:
cli/src/main.rs#L72
no method named `parse` found for struct `Arg` in the current scope
|
test:
cli/src/main.rs#L76
no method named `parse` found for struct `Arg` in the current scope
|
lints:
cli/src/main.rs#L60
cannot find value `try_from_str` in this scope
|
lints:
cli/src/main.rs#L64
cannot find value `try_from_str` in this scope
|
lints:
cli/src/main.rs#L68
cannot find value `try_from_str` in this scope
|
lints:
cli/src/main.rs#L72
cannot find value `try_from_str` in this scope
|
lints:
cli/src/main.rs#L76
cannot find value `try_from_str` in this scope
|
lints:
cli/src/main.rs#L60
no method named `parse` found for struct `clap::Arg` in the current scope
|
lints:
cli/src/main.rs#L64
no method named `parse` found for struct `clap::Arg` in the current scope
|
lints:
cli/src/main.rs#L68
no method named `parse` found for struct `clap::Arg` in the current scope
|
lints:
cli/src/main.rs#L72
no method named `parse` found for struct `clap::Arg` in the current scope
|
lints:
cli/src/main.rs#L76
no method named `parse` found for struct `clap::Arg` in the current scope
|
check
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/
|
check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
check
profiles for the non root package will be ignored, specify profiles at the workspace root:
|
check
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
check:
core/src/util/sentry.rs#L66
field `0` is never read
|
check:
core/src/util/sentry.rs#L67
field `0` is never read
|
check:
core/src/util/sentry.rs#L68
field `0` is never read
|
check
`check-if-email-exists` (lib) generated 3 warnings
|
check
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/
|
check
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/
|
check
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/
|
check
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/
|
test
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/
|
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test
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/
|
test
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/
|
test
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/
|
test
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/
|
test
profiles for the non root package will be ignored, specify profiles at the workspace root:
|
test
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
test:
core/src/util/sentry.rs#L66
field `0` is never read
|
test:
core/src/util/sentry.rs#L67
field `0` is never read
|
test:
core/src/util/sentry.rs#L68
field `0` is never read
|
test
`check-if-email-exists` (lib) generated 3 warnings
|
lints
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/
|
lints
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
lints
profiles for the non root package will be ignored, specify profiles at the workspace root:
|
lints
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
lints:
core/src/util/sentry.rs#L66
field `0` is never read
|
lints:
core/src/util/sentry.rs#L67
field `0` is never read
|
lints:
core/src/util/sentry.rs#L68
field `0` is never read
|
lints:
core/src/lib.rs#L26
doc list item without indentation
|
lints:
core/src/lib.rs#L28
doc list item without indentation
|
lints:
core/src/lib.rs#L30
doc list item without indentation
|
lints:
core/src/lib.rs#L32
doc list item without indentation
|
lints
`check-if-email-exists` (lib) generated 7 warnings
|
lints
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/
|
lints
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/
|
lints
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/
|
lints
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/
|