chore(deps): bump clap from 3.1.18 to 4.1.8

[dependabot[bot]]

Bumps clap from 3.1.18 to 4.1.8.

Release notes

Sourced from clap's releases.

v4.1.8

[4.1.8] - 2023-02-27

Fixes

• (derive) Don't deny lints on the users behalf

v4.1.7

[4.1.7] - 2023-02-27

Fixes

• (derive) Hide some nightly clippy warnings

v4.1.6

[4.1.6] - 2023-02-15

Fixes

• (help) Don't show long help for --help just because hidden possible values include a description

v4.1.4

[4.1.4] - 2023-01-24

Fixes

• (help) Respect disable_colored_help when using arg_required_else_help

Performance

• Speed up compiling arg! macro

v4.1.3

[4.1.3] - 2023-01-23

Fixes

• (error) Improve suggested flag/value/subcommand when two share a long preifx
• (error) When suggesting one of several subcommands, use the plural subcommands, rather than subcommand

v4.1.2

[4.1.2] - 2023-01-23

Fixes

• In documentation, refer to get_flag, rather than get_one::<bool>

v4.1.1

[4.1.1] - 2023-01-14

... (truncated)

Changelog

Sourced from clap's changelog.

[4.1.8] - 2023-02-27

Fixes

• (derive) Don't deny lints on the users behalf

[4.1.7] - 2023-02-27

Fixes

• (derive) Hide some nightly clippy warnings

[4.1.6] - 2023-02-15

Fixes

• (help) Don't show long help for --help just because hidden possible values include a description

[4.1.5] - 2023-02-15

Fixes

• (help) Don't show long help for --help just because a hidden arg has a possible value with a description

[4.1.4] - 2023-01-24

Fixes

• (help) Respect disable_colored_help when using arg_required_else_help

Performance

• Speed up compiling arg! macro

[4.1.3] - 2023-01-23

Fixes

• (error) Improve suggested flag/value/subcommand when two share a long preifx
• (error) When suggesting one of several subcommands, use the plural subcommands, rather than subcommand

[4.1.2] - 2023-01-23

Fixes

• In documentation, refer to get_flag, rather than get_one::<bool>

[4.1.1] - 2023-01-14

Fixes

... (truncated)

Commits

• f931de6 chore: Release
• dbab081 docs: Update changelog
• 70818c3 Merge pull request #4739 from MingweiSamuel/nodeny
• fa76f6f fix: Remove strict linting from generated code
• 5f247f5 chore: Release
• 1999d85 docs: Update changelog
• c3a942e Merge pull request #4735 from rkrasiuk/rkrasiuk/fix-almost-swapped-lint
• 5bab68a fix: Allow clippy::almost_swapped
• 872135b fix: Allow clippy::almost_swapped
• 84a9b53 chore: Release
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated[bot]]

This PR has 154 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Medium
Size       : +124 -30
Percentile : 50.8%

Total files changed: 2

Change summary by file extension:
.lock : +123 -29
.toml : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.