Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update compatible #695

Merged
merged 1 commit into from
Sep 1, 2023
Merged

chore(deps): update compatible #695

merged 1 commit into from
Sep 1, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
anyhow dependencies patch 1.0.71 -> 1.0.75
bstr dependencies minor 1.5.0 -> 1.6.2
clap dependencies minor 4.3.0 -> 4.4.2
git-conventional dependencies patch 0.12.3 -> 0.12.4
globset (source) dependencies patch 0.4.10 -> 0.4.13
once_cell dependencies minor 1.17.2 -> 1.18.0
regex dependencies minor 1.8 -> 1.9
snapbox (source) dev-dependencies patch 0.4.11 -> 0.4.12
toml dependencies patch 0.7.4 -> 0.7.6
toml_edit dependencies patch 0.19.10 -> 0.19.14
trycmd dependencies patch 0.14.16 -> 0.14.17

Release Notes

dtolnay/anyhow (anyhow)

v1.0.75

Compare Source

v1.0.74

Compare Source

v1.0.73

Compare Source

v1.0.72

Compare Source

  • Documentation improvements
BurntSushi/bstr (bstr)

v1.6.2

Compare Source

v1.6.1

Compare Source

v1.6.0

Compare Source

clap-rs/clap (clap)

v4.4.2

Compare Source

Performance
  • Improve build times by removing once_cell dependency

v4.4.1

Compare Source

Features
  • Stabilize Command::styles

v4.4.0

Compare Source

Compatibility
  • Update MSRV to 1.70.0

v4.3.24

Compare Source

Fixes
  • Ensure column padding is preserved in --help with custom templates

v4.3.23

Compare Source

Fixes
  • Fixed UnknownArgumentValueParser to not error on flag's absence

v4.3.22

Compare Source

Features
  • Add UnknownArgumentValueParser for injecting errors for improving the experience with errors

v4.3.21

Compare Source

Features
  • Expose TryMapValueParser so the type can be named

v4.3.20

Compare Source

Features
  • Command::mut_args for modifying all arguments en masse

v4.3.19

Compare Source

Fixes
  • (parse) Respect value_terminator even in the presence of later multiple-value positional arguments

v4.3.18

Compare Source

Fixes
  • (parse) Suggest -- in fewer places where it won't work

v4.3.17

Compare Source

Fixes
  • (help) Address a regression in wrapping PossibleValue descriptions in --help

v4.3.16

Compare Source

Fixes
  • Don't assert when stateful value parsers fail on defaults (e.g. checking if a path exists)

v4.3.15

Compare Source

Features
  • (unstable-styles) Re-export anstyle
Documentation
  • (unstable-styles) Provide more examples

v4.3.14

Compare Source

Features
  • ArgAction::HelpShort and ArgAction::HelpLong for explicitly specifying which style of help to display
Fixes
  • Skip [OPTIONS] in usage if a help or version ArgAction is used

v4.3.13

Compare Source

v4.3.12

Compare Source

Fixes
  • (derive) Don't error on enum variant field attributes

v4.3.11

Compare Source

Features
  • (derive) Support fields wrapped in num::Wrapping, Box, or Arc
  • (derive) Support Box<str>, Box<OsStr>, and Box<Path>

v4.3.10

Compare Source

Performance
  • Drop a dependency, reducing binary size by 1.3 KiB

v4.3.9

Compare Source

Fixes
  • Command::ignore_errors no longer masks help/version

v4.3.8

Compare Source

Fixes
  • Error on ambiguity with infer_long_arg, rather than arbitrarily picking one, matching the documentation and subcommand's behavior

v4.3.7

Compare Source

Documentation
  • Further clarify magic behavior in derive tutorial
  • Further clarify derive API's relationship to builder within the tutorial

v4.3.6

Compare Source

Documentation
  • Suggest clio

v4.3.5

Compare Source

  • ColorChoice::possible_values is added to simplify things for builder users
Fixes
  • ColorChoice::to_possible_value no longer includes descriptions, encouraging shorter help where possible

v4.3.4

Compare Source

Features
  • Add Error::exit_code

v4.3.3

Compare Source

Features
  • Command::defer for delayed initialization of subcommands to reduce startup times of large applications like deno

v4.3.2

Compare Source

Fixes
  • Ensure column padding is preserved in --help with custom templates

v4.3.1

Compare Source

Fixes
  • (parse) Respect value_terminator even in the presence of later multiple-value positional arguments
crate-ci/git-conventional (git-conventional)

v0.12.4

Compare Source

Internal
  • Update dependencies
BurntSushi/ripgrep (globset)

v0.4.13

Compare Source

v0.4.12

Compare Source

v0.4.11

Compare Source

matklad/once_cell (once_cell)

v1.18.0

Compare Source

  • MSRV is updated to 1.60.0 to take advantage of dep: syntax for cargo features,
    removing "implementation details" from publicly visible surface.
rust-lang/regex (regex)

v1.9.4

Compare Source

==================
This is a patch release that fixes a bug where RegexSet::is_match(..) could
incorrectly return false (even when RegexSet::matches(..).matched_any()
returns true).

Bug fixes:

  • BUG #​1070:
    Fix a bug where a prefilter was incorrectly configured for a RegexSet.

v1.9.3

Compare Source

==================
This is a patch release that fixes a bug where some searches could result in
incorrect match offsets being reported. It is difficult to characterize the
types of regexes susceptible to this bug. They generally involve patterns
that contain no prefix or suffix literals, but have an inner literal along with
a regex prefix that can conditionally match.

Bug fixes:

  • BUG #​1060:
    Fix a bug with the reverse inner literal optimization reporting incorrect match
    offsets.

v1.9.2

Compare Source

==================
This is a patch release that fixes another memory usage regression. This
particular regression occurred only when using a RegexSet. In some cases,
much more heap memory (by one or two orders of magnitude) was allocated than in
versions prior to 1.9.0.

Bug fixes:

  • BUG #​1059:
    Fix a memory usage regression when using a RegexSet.

v1.9.1

Compare Source

==================
This is a patch release which fixes a memory usage regression. In the regex
1.9 release, one of the internal engines used a more aggressive allocation
strategy than what was done previously. This patch release reverts to the
prior on-demand strategy.

Bug fixes:

  • BUG #​1027:
    Change the allocation strategy for the backtracker to be less aggressive.

v1.9.0

Compare Source

==================
This release marks the end of a years long rewrite of the regex crate
internals
. Since this is
such a big release, please report any issues or regressions you find. We would
also love to hear about improvements as well.

In addition to many internal improvements that should hopefully result in
"my regex searches are faster," there have also been a few API additions:

  • A new Captures::extract method for quickly accessing the substrings
    that match each capture group in a regex.
  • A new inline flag, R, which enables CRLF mode. This makes . match any
    Unicode scalar value except for \r and \n, and also makes (?m:^) and
    (?m:$) match after and before both \r and \n, respectively, but never
    between a \r and \n.
  • RegexBuilder::line_terminator was added to further customize the line
    terminator used by (?m:^) and (?m:$) to be any arbitrary byte.
  • The std Cargo feature is now actually optional. That is, the regex crate
    can be used without the standard library.
  • Because regex 1.9 may make binary size and compile times even worse, a
    new experimental crate called regex-lite has been published. It prioritizes
    binary size and compile times over functionality (like Unicode) and
    performance. It shares no code with the regex crate.

New features:

  • FEATURE #​244:
    One can opt into CRLF mode via the R flag.
    e.g., (?mR:$) matches just before \r\n.
  • FEATURE #​259:
    Multi-pattern searches with offsets can be done with regex-automata 0.3.
  • FEATURE #​476:
    std is now an optional feature. regex may be used with only alloc.
  • FEATURE #​644:
    RegexBuilder::line_terminator configures how (?m:^) and (?m:$) behave.
  • FEATURE #​675:
    Anchored search APIs are now available in regex-automata 0.3.
  • FEATURE #​824:
    Add new Captures::extract method for easier capture group access.
  • FEATURE #​961:
    Add regex-lite crate with smaller binary sizes and faster compile times.
  • FEATURE #​1022:
    Add TryFrom implementations for the Regex type.

Performance improvements:

  • PERF #​68:
    Added a one-pass DFA engine for faster capture group matching.
  • PERF #​510:
    Inner literals are now used to accelerate searches, e.g., \w+@&#8203;\w+ will scan
    for @.
  • PERF #​787,
    PERF #​891:
    Makes literal optimizations apply to regexes of the form \b(foo|bar|quux)\b.

(There are many more performance improvements as well, but not all of them have
specific issues devoted to them.)

Bug fixes:

  • BUG #​429:
    Fix matching bugs related to \B and inconsistencies across internal engines.
  • BUG #​517:
    Fix matching bug with capture groups.
  • BUG #​579:
    Fix matching bug with word boundaries.
  • BUG #​779:
    Fix bug where some regexes like (re)+ were not equivalent to (re)(re)*.
  • BUG #​850:
    Fix matching bug inconsistency between NFA and DFA engines.
  • BUG #​921:
    Fix matching bug where literal extraction got confused by $.
  • BUG #​976:
    Add documentation to replacement routines about dealing with fallibility.
  • BUG #​1002:
    Use corpus rejection in fuzz testing.

v1.8.4

Compare Source

==================
This is a patch release that fixes a bug where (?-u:\B) was allowed in
Unicode regexes, despite the fact that the current matching engines can report
match offsets between the code units of a single UTF-8 encoded codepoint. That
in turn means that match offsets that split a codepoint could be reported,
which in turn results in panicking when one uses them to slice a &str.

This bug occurred in the transition to regex 1.8 because the underlying
syntactical error that prevented this regex from compiling was intentionally
removed. That's because (?-u:\B) will be permitted in Unicode regexes in
regex 1.9, but the matching engines will guarantee to never report match
offsets that split a codepoint. When the underlying syntactical error was
removed, no code was added to ensure that (?-u:\B) didn't compile in the
regex 1.8 transition release. This release, regex 1.8.4, adds that code
such that Regex::new(r"(?-u:\B)") returns to the regex <1.8 behavior of
not compiling. (A bytes::Regex can still of course compile it.)

Bug fixes:

  • BUG #​1006:
    Fix a bug where (?-u:\B) was allowed in Unicode regexes, and in turn could
    lead to match offsets that split a codepoint in &str.

v1.8.3

Compare Source

==================
This is a patch release that fixes a bug where the regex would report a
match at every position even when it shouldn't. This could occur in a very
small subset of regexes, usually an alternation of simple literals that
have particular properties. (See the issue linked below for a more precise
description.)

Bug fixes:

  • BUG #​999:
    Fix a bug where a match at every position is erroneously reported.

v1.8.2

Compare Source

==================
This is a patch release that fixes a bug where regex compilation could panic
in debug mode for regexes with large counted repetitions. For example,
a{2147483516}{2147483416}{5} resulted in an integer overflow that wrapped
in release mode but panicking in debug mode. Despite the unintended wrapping
arithmetic in release mode, it didn't cause any other logical bugs since the
errant code was for new analysis that wasn't used yet.

Bug fixes:

  • BUG #​995:
    Fix a bug where regex compilation with large counted repetitions could panic.

v1.8.1

Compare Source

==================
This is a patch release that fixes a bug where a regex match could be reported
where none was found. Specifically, the bug occurs when a pattern contains some
literal prefixes that could be extracted and an optional word boundary in the
prefix.

Bug fixes:

  • BUG #​981:
    Fix a bug where a word boundary could interact with prefix literal
    optimizations and lead to a false positive match.
assert-rs/trycmd (snapbox)

v0.4.12

Compare Source

toml-rs/toml (toml)

v0.7.6

Compare Source

v0.7.5

Compare Source


Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) September 1, 2023 00:58
@renovate renovate bot merged commit ef6a698 into master Sep 1, 2023
12 of 15 checks passed
@renovate renovate bot deleted the renovate/compatible branch September 1, 2023 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants