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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update compatible #162

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

chore(deps): update compatible #162

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
anyhow dependencies patch 1.0.71 -> 1.0.94
blake3 dependencies minor 1.3.3 -> 1.5.5
cargo-util dependencies patch 0.2.3 -> 0.2.16
clap dependencies minor 4.3.0 -> 4.5.23
dunce (source) dependencies patch 1.0.4 -> 1.0.5
home dependencies patch 0.5.5 -> 0.5.9
is-terminal dependencies patch 0.4.7 -> 0.4.13
log dependencies patch 0.4.17 -> 0.4.22
regex dependencies minor 1.8.3 -> 1.11.1

Release Notes

dtolnay/anyhow (anyhow)

v1.0.94

Compare Source

  • Documentation improvements

v1.0.93

Compare Source

  • Update dev-dependencies to thiserror v2

v1.0.92

Compare Source

  • Support Rust 1.82's &raw const and &raw mut syntax inside ensure! (#​390)

v1.0.91

Compare Source

  • Ensure OUT_DIR is left with deterministic contents after build script execution (#​388)

v1.0.90

Compare Source

  • Documentation improvements

v1.0.89

Compare Source

  • Make anyhow::Error's UnwindSafe and RefUnwindSafe impl consistently available between versions of Rust newer and older than 1.72 (#​386)

v1.0.88

Compare Source

  • Documentation improvements

v1.0.87

Compare Source

  • Support more APIs, including Error::new and Error::chain, in no-std mode on Rust 1.81+ (#​383)

v1.0.86

Compare Source

  • Fix parse error in ensure! with non-literal after minus sign (#​373)

v1.0.85

Compare Source

  • Improve ensure! macro's rules to unblock some rustc pretty-printer improvements (#​368, #​371)

v1.0.84

Compare Source

  • Disallow calling ensure! through a Not impl for a type that is not bool (#​367)

v1.0.83

Compare Source

  • Integrate compile-time checking of cfgs (#​363)

v1.0.82

Compare Source

  • Documentation improvements

v1.0.81

Compare Source

  • Make backtrace support available when using -Dwarnings (#​354)

v1.0.80

Compare Source

  • Fix unused_imports warnings when compiled by rustc 1.78

v1.0.79

Compare Source

  • Work around improperly cached build script result by sccache (#​340)

v1.0.78

Compare Source

  • Reduce spurious rebuilds under RustRover IDE when using a nightly toolchain (#​337)

v1.0.77

Compare Source

v1.0.76

Compare Source

  • Opt in to unsafe_op_in_unsafe_fn lint (#​329)

v1.0.75

Compare Source

v1.0.74

Compare Source

v1.0.73

Compare Source

v1.0.72

Compare Source

  • Documentation improvements
BLAKE3-team/BLAKE3 (blake3)

v1.5.5

Compare Source

version 1.5.5

Changes since 1.5.4:

  • b3sum --check now supports checkfiles with Windows-style newlines.
    b3sum still emits Unix-style newlines, even on Windows, but
    sometimes text editors or version control tools will swap them.
  • The "digest" feature (deleted in v1.5.2) has been added back to the
    blake3 crate. This is for backwards compatibility only, and it's
    insta-deprecated. All callers should prefer the "traits-preview"
    feature.

v1.5.4

Compare Source

version 1.5.4

Changes since 1.5.3:

  • Initial implementation of SIMD acceleration for the XOF (i.e.
    blake3::Hasher::finalize_xof). This brings long output performance
    into line with long input performance. Currently AVX-512-only and
    Unix-only.
  • Add build support for "gnullvm" targets (Clang on Windows).
  • The "zeroize" feature no longer depends on proc-macros and syn.

v1.5.3

Compare Source

version 1.5.3

Changes since 1.5.2:

  • Revert the serialization change. It was intended to be backwards
    compatible, but that didn't hold for non-self-describing serialization
    formats like bincode. See #​414.

v1.5.2

Compare Source

version 1.5.2

Changes since 1.5.1:

  • build.rs sets cc::Build::emit_rerun_if_env_changed(false) to
    prevent some unnecessary rebuilds, particularly when the PATH
    changes on Windows. See #​324.
  • Serializing a Hash produces a bytestring instead of an array in
    formats that support bytestrings (like CBOR). Deserialization is
    backwards-compatible with the array format.
  • Cleanup and edge case fixes in the C and CMake builds.

v1.5.1

Compare Source

version 1.5.1

Changes since 1.5.0:

  • The Rust crate is now compatible with Miri.
  • ~1% performance improvement on Arm NEON contributed by @​divinity76 (#​384).
  • Various fixes and improvements in the CMake build.
  • The MSRV of b3sum is now 1.74.1. (The MSRV of the library crate is
    unchanged, 1.66.1.)

v1.5.0

Compare Source

version 1.5.0

Changes since 1.4.1:

  • The Rust crate's Hasher type has gained new helper methods for common
    forms of IO: update_reader, update_mmap, and update_mmap_rayon. The
    latter matches the default behavior of b3sum. The mmap methods are
    gated by the new "mmap" Cargo feature.
  • Most of the Rust crate's public types now implement the Zeroize trait.
    This is gated by the new "zeroize" Cargo feature.
  • The Rust crate's Hash types now implements the serde Serialize and
    Deserialize traits. This is gated by the new "serde" Cargo feature.
  • The C library now uses atomics to cache detected CPU features under
    most compilers other than MSVC. Previously this was a non-atomic
    write, which was probably "benign" but made TSan unhappy.
  • NEON support is now disabled by default on big-endian AArch64.
    Previously this was a build error if the caller didn't explicitly
    disable it.

v1.4.1

Compare Source

version 1.4.1

Changes since 1.4.0:

  • Improved performance in the ARM NEON implementation for both C and
    Rust callers. This affects AArch64 targets by default and ARMv7
    targets that explicitly enable (and support) NEON. The size of the
    improvement depends on the microarchitecture, but I've benchmarked
    ~1.3x on a Cortex-A53 and ~1.2x on an Apple M1. Contributed by
    @​sdlyyxy in #​319.
  • The MSRV is now 1.66.1 for both the blake3 crate and b3sum.

v1.4.0

Compare Source

version 1.4.0

Changes since 1.3.3:

  • The C implementation provides a CMakeLists.txt for callers who build
    with CMake. The CMake build is not yet stable, and callers should
    expect breaking changes in patch version updates. The "by hand" build
    will always continue to be supported and documented.
  • b3sum supports the --seek flag, to set the starting position in
    the output stream.
  • b3sum --check prints a summary of errors to stderr.
  • Hash::as_bytes is const.
  • Hash supports from_bytes, which is const.
clap-rs/clap (clap)

v4.5.23

Compare Source

Fixes
  • (parser) When check allow_negative_numbers, allow E again

v4.5.22

Compare Source

Fixes
  • (assert) Catch bugs with arguments requiring themself

v4.5.21

Compare Source

Fixes
  • (parser) Ensure defaults are filled in on error with ignore_errors(true)

v4.5.20

Compare Source

Features
  • (unstable) Add CommandExt

v4.5.19

Compare Source

Internal
  • Update dependencies

v4.5.18

Compare Source

Features
  • (builder) Expose Arg::get_display_order and Command::get_display_order

v4.5.17

Compare Source

Fixes
  • (help) Style required argument groups
  • (derive) Improve error messages when unsupported fields are used

v4.5.16

Compare Source

Fixes
  • (derive) Improve error messages when derive feature is missing

v4.5.15

Compare Source

Compatiblity
  • (unstable-ext) Arg::remove changed return types
Fixes
  • (unstable-ext) Make Arg::remove return the removed item

v4.5.14

Compare Source

Features
  • (unstable-ext) Added Arg::add for attaching arbitrary state, like completion hints, to Arg without Arg knowing about it

v4.5.13

Compare Source

Fixes
  • (derive) Improve error message when #[flatten]ing an optional #[group(skip)]
  • (help) Properly wrap long subcommand descriptions in help

v4.5.12

Compare Source

v4.5.11

Compare Source

v4.5.10

Compare Source

v4.5.9

Compare Source

Fixes
  • (error) When defining a custom help flag, be sure to suggest it like we do the built-in one

v4.5.8

Compare Source

Fixes
  • Reduce extra flushes

v4.5.7

Compare Source

Fixes
  • Clean up error message when too few arguments for num_args

v4.5.6

Compare Source

v4.5.5

Compare Source

Fixes
  • Allow exclusive to override required_unless_present, required_unless_present_any, required_unless_present_all

v4.5.4

Compare Source

Fixes
  • (derive) Allow non-literal #[arg(id)] attributes again

v4.5.3

Compare Source

Internal
  • (derive) Update heck

v4.5.2

Compare Source

Fixes
  • (assert) Catch bugs with arguments requiring themself

v4.5.1

Compare Source

Internal
  • Update dependencies

v4.5.0

Compare Source

Compatibility
  • Update MSRV to 1.74

v4.4.18

Compare Source

Fixes
  • (error) When lacking usage feature, ensure the list of required arguments is unique

v4.4.17

Compare Source

Fixes
  • Fix panic! when mixing args_conflicts_with_subcommands with ArgGroup (which is implicit with derive) introduced in 4.4.15

v4.4.16

Compare Source

Fixes
  • Ensure invalid escape sequences in user-defined strings are correctly stripped when terminal doesn't support color

v4.4.15

Compare Source

Fixes
  • Improve error for args_conflicts_with_subcommands
  • Ensure we error for args_conflicts_with_subcommands when using subcommand short and long flags

v4.4.14

Compare Source

Documentation
  • Fix find cookbook entry to allow repeats of flags/options
Features
  • Allow num_args(0) on options which allows making them emulate being a flag for position-tracking flags

v4.4.13

Compare Source

Documentation
  • Fix link to structopt migration guide

v4.4.12

Compare Source

Performance
  • Only ask TypedValueParser for possible values if needed

v4.4.11

Compare Source

Features
  • Add Command::mut_group

v4.4.10

Compare Source

Documentation
  • Link out to changelog
  • Cross link derive's attribute reference to derive tutorial

v4.4.9

Compare Source

Fixes
  • (help) Show correct Command::about under flattened headings
  • (help) Respect hide when flattening subcommands

v4.4.8

Compare Source

Features
  • Add Command::flatten_help to allow git stash -h like help for subcommands

v4.4.7

Compare Source

Performance
  • Reduced code size

v4.4.6

Compare Source

Internal
  • Upgrade anstream

v4.4.5

Compare Source

Fixes
  • (parser) When inferring subcommand name or long_flag, allow ambiguous-looking matches that unambiguously map back to the same command
  • (parser) When inferring subcommand long_flag, don't panic
  • (assert) Clarify what action is causing a positional that doesn't set values which is especially useful for derive users

v4.4.4

Compare Source

Internal
  • Update terminal_size to 0.3

v4.4.3

Compare Source

Documentation
  • (derive) Clarify use of attributes within the tutorial
  • Split sections in the builder and derive tutorials into separate modules

v4.4.2

Compare Source

Performance
  • Improve build times by removing once_cell dependency

v4.4.1

Compare Source

Fixes
  • (error) When lacking usage feature, ensure the list of required arguments is unique

v4.4.0

Compare Source

compatibility
  • update msrv to 1.70.0

v4.3.24

Compare Source

Fixes
  • Ensure column padding is preserved in --help with custom templates

v4.3.23

Compare Source

Fixes
  • Fixed UnknownArgumentValueParser to not error on flag's absence

v4.3.22

Compare Source

Features
  • Add UnknownArgumentValueParser for injecting errors for improving the experience with errors

v4.3.21

Compare Source

Features
  • Expose TryMapValueParser so the type can be named

v4.3.20

Compare Source

Features
  • Command::mut_args for modifying all arguments en masse

v4.3.19

Compare Source

Fixes
  • (parse) Respect value_terminator even in the presence of later multiple-value positional arguments

v4.3.18

Compare Source

Fixes
  • (parse) Suggest -- in fewer places where it won't work

v4.3.17

Compare Source

Fixes
  • (help) Address a regression in wrapping PossibleValue descriptions in --help

v4.3.16

Compare Source

Fixes
  • Don't assert when stateful value parsers fail on defaults (e.g. checking if a path exists)

v4.3.15

Compare Source

Features
  • (unstable-styles) Re-export anstyle
Documentation
  • (unstable-styles) Provide more examples

v4.3.14

Compare Source

Features
  • ArgAction::HelpShort and ArgAction::HelpLong for explicitly specifying which style of help to display
Fixes
  • Skip [OPTIONS] in usage if a help or version ArgAction is used

v4.3.13

Compare Source

v4.3.12

Compare Source

Fixes
  • (derive) Don't error on enum variant field attributes

v4.3.11

Compare Source

Features
  • (derive) Support fields wrapped in num::Wrapping, Box, or Arc
  • (derive) Support Box<str>, Box<OsStr>, and Box<Path>

v4.3.10

Compare Source

Performance
  • Drop a dependency, reducing binary size by 1.3 KiB

v4.3.9

Compare Source

Fixes
  • Command::ignore_errors no longer masks help/version

v4.3.8

Compare Source

Fixes
  • Error on ambiguity with infer_long_arg, rather than arbitrarily picking one, matching the documentation and subcommand's behavior

v4.3.7

Compare Source

Documentation
  • Further clarify magic behavior in derive tutorial
  • Further clarify derive API's relationship to builder within the tutorial

v4.3.6

Compare Source

Documentation
  • Suggest clio

v4.3.5

Compare Source

  • ColorChoice::possible_values is added to simplify things for builder users
Fixes
  • ColorChoice::to_possible_value no longer includes descriptions, encouraging shorter help where possible

v4.3.4

Compare Source

Features
  • Add Error::exit_code

v4.3.3

Compare Source

Features
  • Command::defer for delayed initialization of subcommands to reduce startup times of large applications like deno

v4.3.2

Compare Source

Fixes
  • Ensure column padding is preserved in --help with custom templates

v4.3.1

Compare Source

Fixes
  • (parse) Respect value_terminator even in the presence of later multiple-value positional arguments
kornelski/dunce (dunce)

v1.0.5

Compare Source

sunfishcode/is-terminal (is-terminal)

v0.4.13

Compare Source

v0.4.12

Compare Source

v0.4.11

Compare Source

v0.4.10

Compare Source

v0.4.9

Compare Source

v0.4.8

Compare Source

rust-lang/log (log)

v0.4.22

Compare Source

v0.4.21

Compare Source

v0.4.20

Compare Source

v0.4.19

Compare Source

v0.4.18

Compare Source

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.

v1.9.6

Compare Source

==================
This is a patch release that fixes a panic that can occur when the default
regex size limit is increased to a large number.

  • BUG aa4e4c71:
    Fix a bug where computing the maximum haystack length for the bounded
    backtracker could result underflow and thus provoke a panic later in a search
    due to a broken invariant.

v1.9.5

Compare Source

==================
This is a patch release that hopefully mostly fixes a performance bug that
occurs when sharing a regex across multiple threads.

Issue #​934
explains this in more detail. It is also noted in the crate
documentation.
The bug can appear when sharing a regex across multiple threads simultaneously,
as might be the case when using a regex from a OnceLock, lazy_static or
similar primitive. Usually high contention only results when using many threads
to execute searches on small haystacks.

One can avoid the contention problem entirely through one of two methods.
The first is to use lower level APIs from regex-automata that require passing
state explicitly, such as meta::Regex::search_with.
The second is to clone a regex and send it to other threads explicitly. This
will not use any additional memory usage compared to sharing the regex. The
only downside of this approach is that it may be less convenient, for example,
it won't work with things like OnceLock or lazy_static or once_cell.

With that said, as of this release, the contention performance problems have
been greatly reduced. This was achieved by changing the free-list so that it
was sharded across threads, and that ensuring each sharded mutex occupies a
single cache line to mitigate false sharing. So while contention may still
impact performance in some cases, it should be a lot better now.

Because of the changes to how the free-list works, please report any issues you
find with this release. That not only includes search time regressions but also
significant regressions in memory usage. Reporting improvements is also welcome
as well! If possible, provide a reproduction.

Bug fixes:

  • BUG #​934:
    Fix a performance bug where high contention on a single regex led to massive
    slow downs.

v1.9.4

Compare Source

==================
This is a patch release that fixes a bug where RegexSet::is_match(..) could
incorrectly return false (even when RegexSet::matches(..).matched_any()
returns true).

Bug fixes:

  • BUG #​1070:
    Fix a bug where a prefilter was incorrectly configured for a RegexSet.

v1.9.3

Compare Source

==================
This is a patch release that fixes a bug where some searches could result in
incorrect match offsets being reported. It is difficult to characterize the
types of regexes susceptible to this bug. They generally involve patterns
that contain no prefix or suffix literals, but have an inner literal along with
a regex prefix that can conditionally match.

Bug fixes:

  • BUG #​1060:
    Fix a bug with the reverse inner literal optimization reporting incorrect match
    offsets.

v1.9.2

Compare Source

==================
This is a patch release that fixes another memory usage regression. This
particular regression occurred only when using a RegexSet. In some cases,
much more heap memory (by one or two orders of magnitude) was allocated than in
versions prior to 1.9.0.

Bug fixes:

  • BUG #​1059:
    Fix a memory usage regression when using a RegexSet.

v1.9.1

Compare Source

==================
This is a patch release which fixes a memory usage regression. In the regex
1.9 release, one of the internal engines used a more aggressive allocation
strategy than what was done previously. This patch release reverts to the
prior on-demand strategy.

Bug fixes:

  • BUG #​1027:
    Change the allocation strategy for the backtracker to be less aggressive.

v1.9.0

Compare Source

==================
This release marks the end of a years long rewrite of the regex crate
internals. Since this is
such a big release, please report any issues or regressions you find. We would
also love to hear about improvements as well.

In addition to many internal improvements that should hopefully result in
"my regex searches are faster," there have also been a few API additions:

  • A new Captures::extract method for quickly accessing the substrings
    that match each capture group in a regex.
  • A new inline flag, R, which enables CRLF mode. This makes . match any
    Unicode scalar value except for \r and \n, and also makes (?m:^) and
    (?m:$) match after and before both \r and \n, respectively, but never
    between a \r and \n.
  • RegexBuilder::line_terminator was added to further customize the line
    terminator used by (?m:^) and (?m:$) to be any arbitrary byte.
  • The std Cargo feature is now actually optional. That is, the regex crate
    can be used without the standard library.
  • Because regex 1.9 may make binary size and compile times even worse, a
    new experimental crate called regex-lite has been published. It prioritizes
    binary size and compile times over functionality (like Unicode) and
    performance. It shares no code with the regex crate.

New features:

  • FEATURE #​244:
    One can opt into CRLF mode via the R flag.
    e.g., (?mR:$) matches just before \r\n.
  • FEATURE #​259:
    Multi-pattern searches with offsets can be done with regex-automata 0.3.
  • FEATURE #​476:
    std is now an optional feature. regex may be used with only alloc.
  • FEATURE #​644:
    RegexBuilder::line_terminator configures how (?m:^) and (?m:$) behave.
  • FEATURE #​675:
    Anchored search APIs are now available in regex-automata 0.3.
  • FEATURE #​824:
    Add new Captures::extract method for easier capture group access.
  • FEATURE #​961:
    Add regex-lite crate with smaller binary sizes and faster compile times.
  • FEATURE #​1022:
    Add TryFrom implementations for the Regex type.

Performance improvements:

  • PERF #​68:
    Added a one-pass DFA engine for faster capture group matching.
  • PERF #​510:
    Inner literals are now used to accelerate searches, e.g., \w+@&#8203;\w+ will scan
    for @.
  • PERF #​787,
    PERF #​891:
    Makes literal optimizations apply to regexes of the form \b(foo|bar|quux)\b.

(There are many more performance improvements as well, but not all of them have
specific issues devoted to them.)

Bug fixes:

  • BUG #​429:
    Fix matching bugs related to \B and inconsistencies across internal engines.
  • BUG #​517:
    Fix matching bug with capture groups.
  • BUG #​579:
    Fix matching bug with word boundaries.
  • BUG #​779:
    Fix bug where some regexes like (re)+ were not equivalent to (re)(re)*.
  • BUG #​850:
    Fix matching bug inconsistency between NFA and DFA engines.
  • BUG #​921:
    Fix matching bug where literal extraction got confused by $.
  • BUG #​976:
    Add documentation to replacement routines about dealing with fallibility.
  • BUG #​1002:
    Use corpus rejection in fuzz testing.

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:

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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/compatible branch from e027d82 to 84bfad5 Compare September 2, 2023 16:20
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from f6d50e1 to d55ccb2 Compare September 19, 2023 16:44
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from 939a2fa to 23ad778 Compare September 25, 2023 23:08
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from 78d582b to 83e1bb4 Compare October 2, 2023 22:04
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from d7191b6 to 1f865e1 Compare October 14, 2023 15:43
@renovate renovate bot force-pushed the renovate/compatible branch from 1f865e1 to 90e02f4 Compare October 16, 2023 15:35
@renovate renovate bot force-pushed the renovate/compatible branch from 90e02f4 to b94469a Compare October 24, 2023 22:38
@renovate renovate bot force-pushed the renovate/compatible branch from b94469a to a84d287 Compare November 11, 2023 00:12
@renovate renovate bot force-pushed the renovate/compatible branch from a84d287 to acd5fc5 Compare November 19, 2023 11:28
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from e6efc05 to f17e83c Compare December 4, 2023 18:50
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from 8a68f7c to 07deb64 Compare December 15, 2023 22:27
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from fc6ff70 to 1540eb3 Compare December 27, 2023 01:52
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from 27bc9b9 to ceaa5ac Compare January 2, 2024 07:51
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from 87a7ce5 to c203835 Compare January 11, 2024 17:27
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from a3932eb to 0ad0de2 Compare May 6, 2024 20:44
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from e7427ae to c247272 Compare May 18, 2024 12:29
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from e40483a to e56a1d7 Compare June 10, 2024 15:37
@renovate renovate bot force-pushed the renovate/compatible branch from e56a1d7 to cf93a03 Compare June 17, 2024 13:58
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from 19d045a to d89df58 Compare June 28, 2024 20:13
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from c3dd089 to 4c024ed Compare July 15, 2024 06:05
@renovate renovate bot force-pushed the renovate/compatible branch 3 times, most recently from 251fffa to 71a8483 Compare July 25, 2024 17:18
@renovate renovate bot force-pushed the renovate/compatible branch 4 times, most recently from ea0cbae to fac86be Compare August 4, 2024 04:50
@renovate renovate bot force-pushed the renovate/compatible branch from fac86be to cc2023e Compare August 8, 2024 17:33
@renovate renovate bot force-pushed the renovate/compatible branch from cc2023e to e48530f Compare August 28, 2024 07:40
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from 5b68207 to bcc9400 Compare September 6, 2024 22:58
@renovate renovate bot force-pushed the renovate/compatible branch 2 times, most recently from 74c621e to f384cca Compare September 15, 2024 03:24
@renovate renovate bot force-pushed the renovate/compatible branch from f384cca to 151d912 Compare September 16, 2024 11:04
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Sep 16, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 4.5.23
warning: `/tmp/renovate/repos/github/epage/cargo-script-mvs/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants