search

sdttttt / gcr

📑 Compact specification git commit tool, it has a variety of practical small functions. (Inspired by git-cz on Node.js)
https://crates.io/crates/grc
The Unlicense
28 stars 6 forks source link

chore(deps): bump clap from 3.1.18 to 4.1.1 #153

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps clap from 3.1.18 to 4.1.1.

Release notes

Sourced from clap's releases.

v4.1.1

[4.1.1] - 2023-01-14

Fixes

  • (error) Small softening attempt for "unexpected argument" error

v4.0.32

[4.0.32] - 2022-12-22

Fixes

  • (parser) When overriding required(true), consider args that conflict with its group

v4.0.31

[4.0.31] - 2022-12-22

Performance

  • Speed up parsing when a lot of different flags are present (100 unique flags)

v4.0.30

[4.0.30] - 2022-12-21

Fixes

  • (error) Improve error for args_conflicts_with_subcommand

v4.0.29

[4.0.29] - 2022-11-29

v4.0.28

[4.0.28] - 2022-11-29

Fixes

  • Fix wasm support which was broken in 4.0.27

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

... (truncated)

Changelog

Sourced from clap's changelog.

[4.1.1] - 2023-01-14

Fixes

  • (error) Small softening attempt for "unexpected argument" error

[4.1.0] - 2023-01-13

Compatibility

MSRV changed to 1.64.0

For apps with custom --help and --version flags:

  • Descriptions for --help and --version changed

When apps have errors imitating clap's error style:

  • Error message style was changed, including
    • Moving away from "did you mean" to tips
    • Leading letter is lower case
    • "For more" added some punctuation

Features

  • ArgMatches::get_occurrences support for argument values to be grouped by their occurrence

Fixes

  • (derive) Allow upgrade_from when arguments / subcommands are explicitly marked as required
  • (help) Try be more clearer and succinct with --help and --version (also helps with overflow)
  • (error) Try to be more clearer and succinct with error messages
  • (error) Officially adopt an error style guide

[4.0.32] - 2022-12-22

Fixes

  • (parser) When overriding required(true), consider args that conflict with its group

[4.0.31] - 2022-12-22

Performance

  • Speed up parsing when a lot of different flags are present (100 unique flags)

[4.0.30] - 2022-12-21

Fixes

  • (error) Improve error for args_conflicts_with_subcommand

... (truncated)

Commits
  • 74a82d7 chore: Release
  • 06f392a docs: Update changelog
  • 4d913fa Merge pull request #4639 from epage/error
  • 162a556 fix(error): Try to soften unexpected argument/value errors
  • 34d856b chore: Release
  • 889ca7a chore: Bump versions for 4.1
  • 2bafb9b docs(contrib): Define a compatibility policy for help/error output
  • a41ca2e docs: Update changelog
  • 523adc2 Merge pull request #4635 from epage/stablize
  • b4f111a feat: Stablize ArgMatches::get_occurrences
  • Additional commits viewable in compare view


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)
pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 143 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 : +116 -27 Percentile : 48.6% Total files changed: 2 Change summary by file extension: .lock : +115 -26 .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 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](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.

dependabot[bot] commented 1 year ago

Superseded by #156.