chore(deps): bump clap from 2.34.0 to 3.1.11

[dependabot[bot]]

Bumps clap from 2.34.0 to 3.1.11.

Release notes

Sourced from clap's releases.

v3.1.11

[3.1.11] - 2022-04-22

Fixes

• Implied conflicts override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
• Members of a mutually exclusive ArgGroup override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
• Arg::overrides_with always override Arg::required, not just when the parser processes an override

v3.1.9

[3.1.9] - 2022-04-15

Fixes

• Pin the clap_derive version so a compatible version is always used with clap

v3.1.8

[3.1.8] - 2022-04-01

Fixes

• Add Debug impls to more types

v3.1.7

[3.1.7] - 2022-03-31

Fixes

• *(derive)* Abort, rather than ignore, when deriving ArgEnum` with non-unit unskipped variants

v3.1.6

[3.1.6] - 2022-03-07

Fixes

• Don't panic when validating delimited defaults (#3541)
• Make it clearer that cargo feature is needed
• Documentation improvements

v3.1.5

[3.1.5] - 2022-03-02

Fixes

• Dependency upgrade

v3.1.4

[3.1.4] - 2022-03-02

Features

... (truncated)

Changelog

Sourced from clap's changelog.

[3.1.11] - 2022-04-22

Fixes

• Implied conflicts override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
• Members of a mutually exclusive ArgGroup override Arg::required, making the behavior consistent with how we calculate conflicts for error reporting
• Arg::overrides_with always override Arg::required, not just when the parser processes an override

[3.1.10] - 2022-04-19

Features

• Expose Command::build for custom help generation or other command introspection needs

[3.1.9] - 2022-04-15

Fixes

• Pin the clap_derive version so a compatible version is always used with clap

[3.1.8] - 2022-04-01

Fixes

• Add Debug impls to more types

[3.1.7] - 2022-03-31

Fixes

• (derive) Abort, rather than ignore, when deriving ArgEnum with non-unit unskipped variants

[3.1.6] - 2022-03-07

Fixes

• Don't panic when validating delimited defaults (#3541)
• Make it clearer that cargo feature is needed
• Documentation improvements

[3.1.5] - 2022-03-02

Fixes

• Dependency upgrade

[3.1.4] - 2022-03-02

Features

... (truncated)

Commits

• a46ee83 chore: Release
• 62e9d2d docs: Update changelog
• 8505c47 refactor(validator): Decouple parser (#3645)
• 9d52301 refactor(validator): Decouple parser
• 6229e78 refactor(parser): Parser is solely responsible for populating ArgMatches
• 02ffd59 refactor(help): Move help writing down a layer
• ebeade9 refactor(help): Consolidate help errors
• 6a9a5d0 refactor(help): Make bool's meaning clearer
• 639f9e8 refactor(parser): Pull out long-help determination
• a484f62 fix(validate): Overrides always ignore required
• 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 79 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Small Size : +53 -26 Percentile : 31.6% Total files changed: 2 Change summary by file extension: .lock : +52 -25 .toml : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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 detetcted. - 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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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.

[sdttttt]

@dependabot ignore this major version

[dependabot[bot]]

OK, I won't notify you about version 3.x.x again, unless you re-open this PR or update to a 3.x.x release yourself.