fix(deps): update rust crate regex to 1.6 #141
Merged
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.5
->1.6
Release Notes
rust-lang/regex
v1.6.0
Compare Source
==================
This release principally includes an upgrade to Unicode 14.
New features:
Clarify that
Captures::len
includes all groups, not just matching groups.Add an
ExactSizeIterator
impl forSubCaptureMatches
.Improve
RegexSet
documentation examples.Upgrade to Unicode 14.
Bug fixes:
Fix error message rendering bug.
v1.5.6
Compare Source
==================
This release includes a few bug fixes, including a bug that produced incorrect
matches when a non-greedy
?
operator was used.Fixes a bug where
[[:alnum:][:^ascii:]]
dropped[:alnum:]
from the class.Fixes a bug where
Hir::is_match_empty
returnedfalse
for\b
.Fixes a bug where 'ab??' matches 'ab' instead of 'a' in 'ab'.
v1.5.5
Compare Source
==================
This releases fixes a security bug in the regex compiler. This bug permits a
vector for a denial-of-service attack in cases where the regex being compiled
is untrusted. There are no known problems where the regex is itself trusted,
including in cases of untrusted haystacks.
Fixes a bug in the regex compiler where empty sub-expressions subverted the
existing mitigations in place to enforce a size limit on compiled regexes.
The Rust Security Response WG published an advisory about this:
https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw
v1.5.4
Compare Source
==================
This release fixes another compilation failure when building regex. This time,
the fix is for when the
pattern
feature is enabled, which only works onnightly Rust. CI has been updated to test this case.
Fix build when
pattern
feature is enabled.v1.5.3
Compare Source
==================
This releases fixes a bug when building regex with only the
unicode-perl
feature. It turns out that while CI was building this configuration, it wasn't
actually failing the overall build on a failed compilation.
Fix build in
regex-syntax
when only theunicode-perl
feature is enabled.v1.5.2
Compare Source
==================
This release fixes a performance bug when Unicode word boundaries are used.
Namely, for certain regexes on certain inputs, it's possible for the lazy DFA
to stop searching (causing a fallback to a slower engine) when it doesn't
actually need to.
PR #768 fixes the bug, which was
originally reported in
ripgrep#1860.
v1.5.1
Compare Source
==================
This is a patch release that fixes a compilation error when the
perf-literal
feature is not enabled.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.