gcr icon indicating copy to clipboard operation
gcr copied to clipboard

chore(deps): bump clap from 3.1.18 to 4.0.26

Open dependabot[bot] opened this issue 3 years ago • 1 comments

Bumps clap from 3.1.18 to 4.0.26.

Release notes

Sourced from clap's releases.

v4.0.26

[4.0.26] - 2022-11-16

Fixes

  • (error) Fix typos in ContextKind::as_str

v4.0.25

[4.0.25] - 2022-11-15

Features

  • (error) Report available subcommands when required subcommand is missing

v4.0.24

[4.0.24] - 2022-11-14

Fixes

  • Avoid panic when printing an argument that isn't built

v4.0.23

[4.0.23] - 2022-11-11

Fixes

  • Don't panic on reporting invalid-long errors when followed by invalid UTF8
  • (help) Clarified argument to help subcommand

v4.0.22

[4.0.22] - 2022-11-07

Fixes

  • (help) Don't overflow into next-line-help early due to stale (pre-v4) padding calculations

v4.0.21

[4.0.21] - 2022-11-07

Features

  • (derive) long_about and long_help attributes, without a value, force using doc comment (before it wouldn't be set if there wasn't anything different than the short help)

v4.0.20

[4.0.20] - 2022-11-07

Fixes

  • (derive) Allow defaulted value parser for '()' fields

... (truncated)

Changelog

Sourced from clap's changelog.

[4.0.26] - 2022-11-16

Fixes

  • (error) Fix typos in ContextKind::as_str

[4.0.25] - 2022-11-15

Features

  • (error) Report available subcommands when required subcommand is missing

[4.0.24] - 2022-11-14

Fixes

  • Avoid panic when printing an argument that isn't built

[4.0.23] - 2022-11-11

Fixes

  • Don't panic on reporting invalid-long errors when followed by invalid UTF8
  • (help) Clarified argument to help subcommand

[4.0.22] - 2022-11-07

Fixes

  • (help) Don't overflow into next-line-help early due to stale (pre-v4) padding calculations

[4.0.21] - 2022-11-07

Features

  • (derive) long_about and long_help attributes, without a value, force using doc comment (before it wouldn't be set if there wasn't anything different than the short help)

[4.0.20] - 2022-11-07

Fixes

  • (derive) Allow defaulted value parser for '()' fields

[4.0.19] - 2022-11-04

Features

  • ColorChoice now implements ValueEnum

[4.0.18] - 2022-10-20

... (truncated)

Commits

Dependabot compatibility score

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)

dependabot[bot] avatar Nov 17 '22 07:11 dependabot[bot]

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


Quantification details

Label      : Extra Small
Size       : +5 -12
Percentile : 6.8%

Total files changed: 2

Change summary by file extension:
.lock : +4 -11
.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.

Superseded by #142.

dependabot[bot] avatar Nov 25 '22 07:11 dependabot[bot]