Update Rust crate regex to v1.12.2 #53
Open
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.9.6->1.12.2Release Notes
rust-lang/regex (regex)
v1.12.2Compare Source
===================
This release fixes a
cargo docbreakage on nightly when--cfg docsrsisenabled. This caused documentation to fail to build on docs.rs.
Bug fixes:
Switches the
doc_auto_cfgfeature todoc_cfgon nightly for docs.rs builds.v1.12.1Compare Source
===================
This release makes a bug fix in the new
regex::Captures::get_matchAPIintroduced in
1.12.0. There was an oversight with the lifetime parameterfor the
Matchreturned. This is technically a breaking change, but giventhat it was caught almost immediately and I've yanked the
1.12.0release,I think this is fine.
v1.12.0Compare Source
===================
This release contains a smattering of bug fixes, a fix for excessive memory
consumption in some cases and a new
regex::Captures::get_matchAPI.Improvements:
Add
Capture::get_matchfor returning the overall match withoutunwrap().Bug fixes:
Fixes a panic in the lazy DFA (can only occur for especially large regexes).
Fixes a memory usage regression for large regexes (introduced in
regex 1.9).Fix universal start states in sparse DFA.
Fixes a panic when deserializing a corrupted dense DFA.
Make
regex_automata::meta::Regex::findconsistently returnNonewhenWhichCaptures::Noneis used.v1.11.3Compare Source
===================
This is a small patch release with an improvement in memory usage in some
cases.
Improvements:
Improve memory usage by trimming excess memory capacity in some spots.
v1.11.2Compare Source
===================
This is a new patch release of
regexwith some minor fixes. A larger numberof typo or lint fix patches were merged. Also, we now finally recommend using
std::sync::LazyLock.Improvements:
Switch recommendation from
once_celltostd::sync::LazyLock.Add
DFA::set_prefiltertoregex-automata.Bug fixes:
Remove
stddependency fromperf-literal-multisubstringcrate feature.Clarify the meaning of
(?R)$in the documentation.Remove
fuzz/andrecord/directories from published crate on crates.io.v1.11.1Compare Source
===================
This is a new patch release of
regexthat fixes compilation on nightlyRust when the unstable
patterncrate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.v1.11.0Compare Source
===================
This is a new minor release of
regexthat brings in an update to theUnicode Character Database. Specifically, this updates the Unicode data
used by
regexinternally to the version 16 release.New features:
Add new
regex::SetMatches::matched_allmethod.Update to Unicode Character Database (UCD) version 16.
v1.10.6Compare Source
===================
This is a new patch release with a fix for the
unstablecrate feature thatenables
std::str::Patterntrait integration.Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.v1.10.5Compare Source
===================
This is a new patch release with some minor fixes.
Bug fixes:
Escape invalid UTF-8 when in the
Debugimpl ofregex::bytes::Match.v1.10.4Compare Source
===================
This is a new patch release with some minor fixes.
Fixes a bug with compiling a reverse NFA automaton in
regex-automata.Clarifies that when
Cow::Borrowedis returned from replace APIs, it isequivalent to the input.
v1.10.3Compare Source
===================
This is a new patch release that fixes the feature configuration of optional
dependencies, and fixes an unsound use of bounds check elision.
Bug fixes:
Set
default-features=falsefor thememchrandaho-corasickdependencies.Fix unsound bounds check elision.
v1.10.2Compare Source
===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.
Bug fixes:
Revert broadening of reverse suffix literal optimization introduced in 1.10.1.
v1.10.1Compare Source
===================
This is a new patch release with a minor increase in the number of valid
patterns and a broadening of some literal optimizations.
New features:
Loosen ASCII-compatible rules such that regexes like
(?-u:☃)are now allowed.Performance improvements:
Broader the reverse suffix optimization to apply in more cases.
v1.10.0Compare Source
===================
This is a new minor release of
regexthat adds support for start and endword boundary assertions. That is,
\<and\>. The minimum supported Rustversion has also been raised to 1.65, which was released about one year ago.
The new word boundary assertions are:
\<or\b{start}: a Unicode start-of-word boundary (\W|\Aon the left,\won the right).\>or\b{end}: a Unicode end-of-word boundary (\won the left,\W|\zon the right).
\b{start-half}: half of a Unicode start-of-word boundary (\W|\Aon theleft).
\b{end-half}: half of a Unicode end-of-word boundary (\W|\zon theright).
The
\<and\>are GNU extensions to POSIX regexes. They have been addedto the
regexcrate because they enjoy somewhat broad support in other regexengines as well (for example, vim). The
\b{start}and\b{end}assertionsare aliases for
\<and\>, respectively.The
\b{start-half}and\b{end-half}assertions are not found in anyother regex engine (although regex engines with general look-around support
can certainly express them). They were added principally to support the
implementation of word matching in grep programs, where one generally wants to
be a bit more flexible in what is considered a word boundary.
New features:
Add support for
\<and\>word boundary assertions.DFAs now have a
start_statemethod that doesn't use anInput.Performance improvements:
Unicode character class operations have been optimized in
regex-syntax.Make patterns containing lots of literal characters use less memory.
Bug fixes:
Fix a bug that could result in incorrect match spans when using a Unicode word
boundary and searching non-ASCII strings.
Fix panics that can occur in
Ast->Hirtranslation (not reachable fromregexcrate).
Remove guarantees in the API that connect the
uflag with a specific HIRrepresentation.
regex-automatabreaking change release:This release includes a
regex-automata 0.4.0breaking change release, whichwas necessary in order to support the new word boundary assertions. For
example, the
Lookenum has new variants and theLookSettype now usesu32instead of
u16to represent a bitset of look-around assertions. These areoverall very minor changes, and most users of
regex-automatashould be ableto move to
0.4from0.3without any changes at all.regex-syntaxbreaking change release:This release also includes a
regex-syntax 0.8.0breaking change release,which, like
regex-automata, was necessary in order to support the new wordboundary assertions. This release also includes some changes to the
Asttype to reduce heap usage in some cases. If you are using the
Asttypedirectly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7should be able to migrate to0.8without any code changes.regex-literelease:The
regex-lite 0.1.1release contains support for the new word boundaryassertions. There are no breaking changes.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.