chore(deps): update compatible #343
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.0.0->1.0.24.3->4.41.0.0->1.0.21.1.4->1.2.01.0.4->1.0.51.17.2->1.18.01.8->1.92.6.0->2.7.0Release Notes
rust-cli/anstyle (anstyle)
v1.0.2Compare Source
v1.0.1Compare Source
clap-rs/clap (clap)
v4.4.2Compare Source
Performance
once_celldependencyv4.4.1Compare Source
Features
Command::stylesv4.4.0Compare Source
Compatibility
v4.3.24Compare Source
Fixes
--helpwith custom templatesv4.3.23Compare Source
Fixes
UnknownArgumentValueParserto not error on flag's absencev4.3.22Compare Source
Features
UnknownArgumentValueParserfor injecting errors for improving the experience with errorsv4.3.21Compare Source
Features
TryMapValueParserso the type can be namedv4.3.20Compare Source
Features
Command::mut_argsfor modifying all arguments en massev4.3.19Compare Source
Fixes
value_terminatoreven in the presence of later multiple-value positional argumentsv4.3.18Compare Source
Fixes
--in fewer places where it won't workv4.3.17Compare Source
Fixes
PossibleValuedescriptions in--helpv4.3.16Compare Source
Fixes
v4.3.15Compare Source
Features
anstyleDocumentation
v4.3.14Compare Source
Features
ArgAction::HelpShortandArgAction::HelpLongfor explicitly specifying which style of help to displayFixes
[OPTIONS]in usage if a help or versionArgActionis usedv4.3.13Compare Source
v4.3.12Compare Source
Fixes
v4.3.11Compare Source
Features
num::Wrapping,Box, orArcBox<str>,Box<OsStr>, andBox<Path>v4.3.10Compare Source
Performance
v4.3.9Compare Source
Fixes
Command::ignore_errorsno longer masks help/versionv4.3.8Compare Source
Fixes
infer_long_arg, rather than arbitrarily picking one, matching the documentation and subcommand's behaviorv4.3.7Compare Source
Documentation
v4.3.6Compare Source
Documentation
cliov4.3.5Compare Source
ColorChoice::possible_valuesis added to simplify things for builder usersFixes
ColorChoice::to_possible_valueno longer includes descriptions, encouraging shorter help where possiblev4.3.4Compare Source
Features
Error::exit_codev4.3.3Compare Source
Features
Command::deferfor delayed initialization of subcommands to reduce startup times of large applications like denov4.3.2Compare Source
Fixes
--helpwith custom templatesv4.3.1Compare Source
Fixes
value_terminatoreven in the presence of later multiple-value positional argumentsrust-cli/human-panic (human-panic)
v1.2.0Compare Source
Compatibility
Performance
is-terminaldependencyv1.1.5Compare Source
Fixes
crate-ci/imperative (imperative)
v1.0.5Compare Source
Fixes
packageaddedis not imperativematklad/once_cell (once_cell)
v1.18.0Compare Source
MSRVis updated to 1.60.0 to take advantage ofdep:syntax for cargo features,removing "implementation details" from publicly visible surface.
rust-lang/regex (regex)
v1.9.4Compare Source
==================
This is a patch release that fixes a bug where
RegexSet::is_match(..)couldincorrectly return false (even when
RegexSet::matches(..).matched_any()returns true).
Bug fixes:
Fix a bug where a prefilter was incorrectly configured for a
RegexSet.v1.9.3Compare 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:
Fix a bug with the reverse inner literal optimization reporting incorrect match
offsets.
v1.9.2Compare 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:
Fix a memory usage regression when using a
RegexSet.v1.9.1Compare 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:
Change the allocation strategy for the backtracker to be less aggressive.
v1.9.0Compare 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:
Captures::extractmethod for quickly accessing the substringsthat match each capture group in a regex.
R, which enables CRLF mode. This makes.match anyUnicode scalar value except for
\rand\n, and also makes(?m:^)and(?m:$)match after and before both\rand\n, respectively, but neverbetween a
\rand\n.RegexBuilder::line_terminatorwas added to further customize the lineterminator used by
(?m:^)and(?m:$)to be any arbitrary byte.stdCargo feature is now actually optional. That is, theregexcratecan be used without the standard library.
regex 1.9may make binary size and compile times even worse, anew experimental crate called
regex-litehas been published. It prioritizesbinary size and compile times over functionality (like Unicode) and
performance. It shares no code with the
regexcrate.New features:
One can opt into CRLF mode via the
Rflag.e.g.,
(?mR:$)matches just before\r\n.Multi-pattern searches with offsets can be done with
regex-automata 0.3.stdis now an optional feature.regexmay be used with onlyalloc.RegexBuilder::line_terminatorconfigures how(?m:^)and(?m:$)behave.Anchored search APIs are now available in
regex-automata 0.3.Add new
Captures::extractmethod for easier capture group access.Add
regex-litecrate with smaller binary sizes and faster compile times.Add
TryFromimplementations for theRegextype.Performance improvements:
Added a one-pass DFA engine for faster capture group matching.
Inner literals are now used to accelerate searches, e.g.,
\w+@​\w+will scanfor
@.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:
Fix matching bugs related to
\Band inconsistencies across internal engines.Fix matching bug with capture groups.
Fix matching bug with word boundaries.
Fix bug where some regexes like
(re)+were not equivalent to(re)(re)*.Fix matching bug inconsistency between NFA and DFA engines.
Fix matching bug where literal extraction got confused by
$.Add documentation to replacement routines about dealing with fallibility.
Use corpus rejection in fuzz testing.
v1.8.4Compare Source
==================
This is a patch release that fixes a bug where
(?-u:\B)was allowed inUnicode 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.8because the underlyingsyntactical error that prevented this regex from compiling was intentionally
removed. That's because
(?-u:\B)will be permitted in Unicode regexes inregex 1.9, but the matching engines will guarantee to never report matchoffsets that split a codepoint. When the underlying syntactical error was
removed, no code was added to ensure that
(?-u:\B)didn't compile in theregex 1.8transition release. This release,regex 1.8.4, adds that codesuch that
Regex::new(r"(?-u:\B)")returns to theregex <1.8behavior ofnot compiling. (A
bytes::Regexcan still of course compile it.)Bug fixes:
Fix a bug where
(?-u:\B)was allowed in Unicode regexes, and in turn couldlead to match offsets that split a codepoint in
&str.v1.8.3Compare 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:
Fix a bug where a match at every position is erroneously reported.
v1.8.2Compare 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 wrappedin 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:
Fix a bug where regex compilation with large counted repetitions could panic.
v1.8.1Compare 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:
Fix a bug where a word boundary could interact with prefix literal
optimizations and lead to a false positive match.
seanmonstar/unicase (unicase)
v2.7.0Compare Source
What's Changed
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.
This PR has been generated by Mend Renovate. View repository job log here.