gcr icon indicating copy to clipboard operation
gcr copied to clipboard

chore(deps): bump console from 0.15.0 to 0.15.5

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

Bumps console from 0.15.0 to 0.15.5.

Changelog

Sourced from console's changelog.

0.15.5

Enhancements

  • Removed regex dependency. (#153)
  • Clarified that clicolors-control is no longer used.
  • Handle non-tty terminals in read_char. (#124)

0.15.4

Enhancements

  • Fix for regression where console size was misreported on windows. (#151)

0.15.3

Enhancements

  • Dropped terminal_size dependency.

0.15.2

Enhancements

  • Dropped once_cell dependency to support MSRV again.

0.15.1

Enhancements

  • ANSI support no longer depends on regex crate.
  • Crate now supports minver.
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 Jan 16 '23 07:01 dependabot[bot]

This PR has 88 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       : +59 -29
Percentile : 35.2%

Total files changed: 2

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

Codecov Report

Base: 51.81% // Head: 38.78% // Decreases project coverage by -13.03% :warning:

Coverage data is based on head (2a713a4) compared to base (2aaadf2). Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #152       +/-   ##
===========================================
- Coverage   51.81%   38.78%   -13.04%     
===========================================
  Files          10       10               
  Lines         577      446      -131     
===========================================
- Hits          299      173      -126     
+ Misses        278      273        -5     
Impacted Files Coverage Δ
src/util.rs 66.66% <0.00%> (-13.71%) :arrow_down:
src/extensions.rs 79.41% <0.00%> (-8.31%) :arrow_down:
src/arguments.rs 81.53% <0.00%> (-5.06%) :arrow_down:
src/message.rs 13.04% <0.00%> (-4.99%) :arrow_down:
src/config.rs 71.79% <0.00%> (-2.68%) :arrow_down:
src/log.rs 100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

codecov[bot] avatar Jan 16 '23 07:01 codecov[bot]