Update all dependencies #35
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
4.3.0->4.3.51.8.1->1.8.4Release Notes
clap-rs/clap
v4.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
unused_equalificationswarnings when someone brings a clap type into scopev4.3.1Compare Source
Performance
rust-lang/regex
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 Renovate Bot.
Update Rust crate regex to 1.8.2to Update Rust crate regex to 1.8.365c4406356toee69397084Update Rust crate regex to 1.8.3to Update all dependenciesee69397084to912b26e2ee912b26e2eetoc5d5e61463c5d5e61463to806e18ea35806e18ea35toa4c07ffe60