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

fix(deps): update rust crate regex to 1.8 #154

Merged
merged 1 commit into from
Jun 19, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 5, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
regex dependencies minor 1.6 -> 1.8

Release Notes

rust-lang/regex

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

==================
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.

v1.8.0

==================
This is a sizeable release that will be soon followed by another sizeable
release. Both of them will combined close over 40 existing issues and PRs.

This first release, despite its size, essentially represents preparatory work
for the second release, which will be even bigger. Namely, this release:

  • Increases the MSRV to Rust 1.60.0, which was released about 1 year ago.
  • Upgrades its dependency on aho-corasick to the recently released 1.0
    version.
  • Upgrades its dependency on regex-syntax to the simultaneously released
    0.7 version. The changes to regex-syntax principally revolve around a
    rewrite of its literal extraction code and a number of simplifications and
    optimizations to its high-level intermediate representation (HIR).

The second release, which will follow ~shortly after the release above, will
contain a soup-to-nuts rewrite of every regex engine. This will be done by
bringing regex-automata into
this repository, and then changing the regex crate to be nothing but an API
shim layer on top of regex-automata's API.

These tandem releases are the culmination of about 3
years of on-and-off work that began in earnest in March
2020
.

Because of the scale of changes involved in these releases, I would love to
hear about your experience. Especially if you notice undocumented changes in
behavior or performance changes (positive or negative).

Most changes in the first release are listed below. For more details, please
see the commit log, which reflects a linear and decently documented history
of all changes.

New features:

  • FEATURE #​501:
    Permit many more characters to be escaped, even if they have no significance.
    More specifically, any ASCII character except for [0-9A-Za-z<>] can now be
    escaped. Also, a new routine, is_escapeable_character, has been added to
    regex-syntax to query whether a character is escapeable or not.
  • FEATURE #​547:
    Add Regex::captures_at. This filles a hole in the API, but doesn't otherwise
    introduce any new expressive power.
  • FEATURE #​595:
    Capture group names are now Unicode-aware. They can now begin with either a _
    or any "alphabetic" codepoint. After the first codepoint, subsequent codepoints
    can be any sequence of alpha-numeric codepoints, along with _, ., [ and
    ]. Note that replacement syntax has not changed.
  • FEATURE #​810:
    Add Match::is_empty and Match::len APIs.
  • FEATURE #​905:
    Add an impl Default for RegexSet, with the default being the empty set.
  • FEATURE #​908:
    A new method, Regex::static_captures_len, has been added which returns the
    number of capture groups in the pattern if and only if every possible match
    always contains the same number of matching groups.
  • FEATURE #​955:
    Named captures can now be written as (?<name>re) in addition to
    (?P<name>re).
  • FEATURE: regex-syntax now supports empty character classes.
  • FEATURE: regex-syntax now has an optional std feature. (This will come
    to regex in the second release.)
  • FEATURE: The Hir type in regex-syntax has had a number of simplifications
    made to it.
  • FEATURE: regex-syntax has support for a new R flag for enabling CRLF
    mode. This will be supported in regex proper in the second release.
  • FEATURE: regex-syntax now has proper support for "regex that never
    matches" via Hir::fail().
  • FEATURE: The hir::literal module of regex-syntax has been completely
    re-worked. It now has more documentation, examples and advice.
  • FEATURE: The allow_invalid_utf8 option in regex-syntax has been renamed
    to utf8, and the meaning of the boolean has been flipped.

Performance improvements:

  • PERF: The upgrade to aho-corasick 1.0 may improve performance in some
    cases. It's difficult to characterize exactly which patterns this might impact,
    but if there are a small number of longish (>= 4 bytes) prefix literals, then
    it might be faster than before.

Bug fixes:

  • BUG #​514:
    Improve Debug impl for Match so that it doesn't show the entire haystack.
  • BUGS #​516,
    #​731:
    Fix a number of issues with printing Hir values as regex patterns.
  • BUG #​610:
    Add explicit example of foo|bar in the regex syntax docs.
  • BUG #​625:
    Clarify that SetMatches::len does not (regretably) refer to the number of
    matches in the set.
  • BUG #​660:
    Clarify "verbose mode" in regex syntax documentation.
  • BUG #​738,
    #​950:
    Fix CaptureLocations::get so that it never panics.
  • BUG #​747:
    Clarify documentation for Regex::shortest_match.
  • BUG #​835:
    Fix \p{Sc} so that it is equivalent to \p{Currency_Symbol}.
  • BUG #​846:
    Add more clarifying documentation to the CompiledTooBig error variant.
  • BUG #​854:
    Clarify that regex::Regex searches as if the haystack is a sequence of
    Unicode scalar values.
  • BUG #​884:
    Replace __Nonexhaustive variants with #[non_exhaustive] attribute.
  • BUG #​893:
    Optimize case folding since it can get quite slow in some pathological cases.
  • BUG #​895:
    Reject (?-u:\W) in regex::Regex APIs.
  • BUG #​942:
    Add a missing void keyword to indicate "no parameters" in C API.
  • BUG #​965:
    Fix \p{Lc} so that it is equivalent to \p{Cased_Letter}.
  • BUG #​975:
    Clarify documentation for \pX syntax.

v1.7.3

Compare Source

==================
This is a small release that fixes a bug in Regex::shortest_match_at that
could cause it to panic, even when the offset given is valid.

Bug fixes:

  • BUG #​969:
    Fix a bug in how the reverse DFA was called for Regex::shortest_match_at.

v1.7.2

Compare Source

==================
This is a small release that fixes a failing test on FreeBSD.

Bug fixes:

  • BUG #​967:
    Fix "no stack overflow" test which can fail due to the small stack size.

v1.7.1

Compare Source

==================
This release was done principally to try and fix the doc.rs rendering for the
regex crate.

Performance improvements:

  • PERF #​930:
    Optimize replacen. This also applies to replace, but not replace_all.

Bug fixes:

  • BUG #​945:
    Maybe fix rustdoc rendering by just bumping a new release?

v1.7.0

Compare Source

==================
This release principally includes an upgrade to Unicode 15.

New features:


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.


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

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

@netlify
Copy link

netlify bot commented Nov 5, 2022

Deploy Preview for hoard-docs ready!

Name Link
🔨 Latest commit 2ae3ab2
🔍 Latest deploy log https://app.netlify.com/sites/hoard-docs/deploys/648f6a4e42d1b400082c4cba
😎 Deploy Preview https://deploy-preview-154--hoard-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@codecov
Copy link

codecov bot commented Nov 5, 2022

Codecov Report

Merging #154 (2ae3ab2) into main (8dfb744) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #154   +/-   ##
=======================================
  Coverage   90.17%   90.17%           
=======================================
  Files          73       73           
  Lines        5108     5108           
=======================================
  Hits         4606     4606           
  Misses        502      502           

@renovate renovate bot force-pushed the renovate/regex-1.x branch 2 times, most recently from 0d267b9 to e615b65 Compare March 24, 2023 07:57
@renovate renovate bot changed the title fix(deps): update rust crate regex to 1.7 fix(deps): update rust crate regex to 1.8 Apr 21, 2023
@Shadow53 Shadow53 merged commit 39090d1 into main Jun 19, 2023
@renovate renovate bot deleted the renovate/regex-1.x branch June 19, 2023 10:31
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.

1 participant