Skip to content

Update Rust crate regex to v1.11.1 #53

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2024

This PR contains the following updates:

Package Type Update Change
regex dependencies minor 1.9.6 -> 1.11.1

Release Notes

rust-lang/regex (regex)

v1.11.1

Compare Source

===================
This is a new patch release of regex that fixes compilation on nightly
Rust when the unstable pattern crate feature is enabled. Users on nightly
Rust without this feature enabled are unaffected.

Bug fixes:

  • BUG #​1231:
    Fix the Pattern trait implementation as a result of nightly API breakage.

v1.11.0

Compare Source

===================
This is a new minor release of regex that brings in an update to the
Unicode Character Database. Specifically, this updates the Unicode data
used by regex internally to the version 16 release.

New features:

v1.10.6

Compare Source

===================
This is a new patch release with a fix for the unstable crate feature that
enables std::str::Pattern trait integration.

Bug fixes:

  • BUG #​1219:
    Fix the Pattern trait implementation as a result of nightly API breakage.

v1.10.5

Compare Source

===================
This is a new patch release with some minor fixes.

Bug fixes:

  • BUG #​1203:
    Escape invalid UTF-8 when in the Debug impl of regex::bytes::Match.

v1.10.4

Compare Source

===================
This is a new patch release with some minor fixes.

  • BUG #​1169:
    Fixes a bug with compiling a reverse NFA automaton in regex-automata.
  • BUG #​1178:
    Clarifies that when Cow::Borrowed is returned from replace APIs, it is
    equivalent to the input.

v1.10.3

Compare 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:

  • BUG #​1147:
    Set default-features=false for the memchr and aho-corasick dependencies.
  • BUG #​1154:
    Fix unsound bounds check elision.

v1.10.2

Compare Source

===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.

Bug fixes:

  • BUG #​1110:
    Revert broadening of reverse suffix literal optimization introduced in 1.10.1.

v1.10.1

Compare 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:

  • FEATURE 04f5d7be:
    Loosen ASCII-compatible rules such that regexes like (?-u:☃) are now allowed.

Performance improvements:

  • PERF 8a8d599f:
    Broader the reverse suffix optimization to apply in more cases.

v1.10.0

Compare Source

===================
This is a new minor release of regex that adds support for start and end
word boundary assertions. That is, \< and \>. The minimum supported Rust
version 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|\A on the left,
    \w on the right).
  • \> or \b{end}: a Unicode end-of-word boundary (\w on the left, \W|\z
    on the right)).
  • \b{start-half}: half of a Unicode start-of-word boundary (\W|\A on the
    left).
  • \b{end-half}: half of a Unicode end-of-word boundary (\W|\z on the
    right).

The \< and \> are GNU extensions to POSIX regexes. They have been added
to the regex crate because they enjoy somewhat broad support in other regex
engines as well (for example, vim). The \b{start} and \b{end} assertions
are aliases for \< and \>, respectively.

The \b{start-half} and \b{end-half} assertions are not found in any
other 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:

Performance improvements:

  • PERF #​1051:
    Unicode character class operations have been optimized in regex-syntax.
  • PERF #​1090:
    Make patterns containing lots of literal characters use less memory.

Bug fixes:

  • BUG #​1046:
    Fix a bug that could result in incorrect match spans when using a Unicode word
    boundary and searching non-ASCII strings.
  • BUG(regex-syntax) #​1047:
    Fix panics that can occur in Ast->Hir translation (not reachable from regex
    crate).
  • BUG(regex-syntax) #​1088:
    Remove guarantees in the API that connect the u flag with a specific HIR
    representation.

regex-automata breaking change release:

This release includes a regex-automata 0.4.0 breaking change release, which
was necessary in order to support the new word boundary assertions. For
example, the Look enum has new variants and the LookSet type now uses u32
instead of u16 to represent a bitset of look-around assertions. These are
overall very minor changes, and most users of regex-automata should be able
to move to 0.4 from 0.3 without any changes at all.

regex-syntax breaking change release:

This release also includes a regex-syntax 0.8.0 breaking change release,
which, like regex-automata, was necessary in order to support the new word
boundary assertions. This release also includes some changes to the Ast
type to reduce heap usage in some cases. If you are using the Ast type
directly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7 should be able to migrate to 0.8 without any code changes.

regex-lite release:

The regex-lite 0.1.1 release contains support for the new word boundary
assertions. 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from d888501 to b888380 Compare May 6, 2024 16:11
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from b888380 to dcb5a7c Compare June 9, 2024 13:48
@renovate renovate bot changed the title Update Rust crate regex to v1.10.4 Update Rust crate regex to v1.10.5 Jun 9, 2024
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from dcb5a7c to 379ac24 Compare June 22, 2024 03:56
@renovate renovate bot changed the title Update Rust crate regex to v1.10.5 Update Rust crate regex to v1.10.6 Aug 2, 2024
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from 379ac24 to ce9881d Compare August 2, 2024 16:08
@renovate renovate bot changed the title Update Rust crate regex to v1.10.6 Update Rust crate regex to v1.11.0 Sep 29, 2024
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from ce9881d to a1f4f57 Compare September 29, 2024 15:53
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from a1f4f57 to 29ad7c3 Compare October 24, 2024 15:09
@renovate renovate bot changed the title Update Rust crate regex to v1.11.0 Update Rust crate regex to v1.11.1 Oct 24, 2024
@renovate renovate bot force-pushed the renovate/regex-1.x-lockfile branch from 29ad7c3 to 87ec133 Compare December 30, 2024 21: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.

0 participants