Open
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #62 +/- ##
==========================================
+ Coverage 46.60% 46.92% +0.31%
==========================================
Files 6 6
Lines 339 341 +2
==========================================
+ Hits 158 160 +2
Misses 181 181 ☔ View full report in Codecov by Sentry. |
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
143fd1f to
3bbf9c6
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
3bbf9c6 to
ea2640a
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
1891fc6 to
544ffde
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
544ffde to
7cd99c4
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
7cd99c4 to
99f0f32
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
2affed1 to
cba4172
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
97a1507 to
cfae54d
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
4 times, most recently
from
5ed44fe to
a9ed325
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
a9ed325 to
d60a552
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
3 times, most recently
from
e15ceaa to
c42f1f7
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
0536a84 to
6e408bd
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
3 times, most recently
from
becf011 to
bb1582a
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
bb1582a to
6f8e412
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
0ae90a3 to
6c77f79
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
cecb539 to
4736d54
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
a846def to
b368826
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
b368826 to
02c011d
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
4 times, most recently
from
4733a81 to
4f02a1d
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
3 times, most recently
from
542c76d to
c22b2fe
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
3 times, most recently
from
06be6aa to
177e956
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
177e956 to
1115a3d
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
1115a3d to
0990811
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
0990811 to
984c454
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
4 times, most recently
from
c2c0352 to
d55f1bc
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
d55f1bc to
bfe48db
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
bfe48db to
a630822
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
997546a to
e7e1850
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
2 times, most recently
from
b9d7903 to
3c2e837
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
3c2e837 to
69c11a9
Compare
renovate
Bot
force-pushed
the
renovate/cargo-dependencies
branch
from
69c11a9 to
994f2d1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
0.13.1→0.15.04.3.3→4.5.01.16.0→1.21.41.7.0→1.12.30.15.0→0.26.00.18.0→0.21.00.10.2→0.20.03.3.0→3.27.0Release Notes
rust-cli/config-rs (config)
v0.15.22Compare Source
Documentation
Internal
v0.15.21Compare Source
Compatibility
v0.15.20Compare Source
Fixes
u64rangeInternal
v0.15.19Compare Source
Internal
v0.15.18Compare Source
Fixes
v0.15.17Compare Source
Features
v0.15.16Compare Source
Performance
serde_corev0.15.15Compare Source
Fixes
null(regressed in 0.15.14)v0.15.14Compare Source
Performance
v0.15.13Compare Source
Fixes
v0.15.12Compare Source
Performance
tomlv0.9v0.15.11Compare Source
Features
v0.15.10Compare Source
Features
Fixes
v0.15.9Compare Source
Compatibility
yaml-rust20.10Documentation
v0.15.8Compare Source
Fix
v0.15.7Compare Source
Internal
v0.15.6Compare Source
Fixes
v0.15.5Compare Source
Fixes
keyon all serde errorsPerformance
v0.15.4Compare Source
Performance
v0.15.3Compare Source
Fixes
v0.15.2Compare Source
Fixes
v0.15.1Compare Source
Internal
v0.15.0Compare Source
Compatibility
ConfigErroris no longer exhaustiveConfigError::Parses type changedFileFormatis no longer exhaustiveFixes
v0.14.1Compare Source
Compatibility
Internal
lazy_staticv0.14.0Compare Source
This is a maintenance release, mostly to get some dependency updates out, but
also with some fixes and changes that have piled up over a rather long time.
Features
Fixes
Dependency updates
Misc
v0.13.4Compare Source
v0.13.3Compare Source
Please note that we had to update the MSRV for this crate from 1.56.0 to 1.59.0
for this patch release being possible, because a transitive dependency did
update its MSRV.
using float_cmp for testing floats
Clonetrait derive to builder statesv0.13.2Compare Source
be able to backport the next change. This change shouldn't be user-visible.
integers
fix tests
sunng87/handlebars-rust (handlebars)
v4.5.0Compare Source
v4.4.0Compare Source
v4.3.7Compare Source
Resultinhandlebars_helpermacro [#578]v4.3.6Compare Source
[Fixed] Loading template files with multiple extensions, a bug introduced in 4.3.0 when refactoring directory source.
v4.3.5Compare Source
v4.3.4Compare Source
write_fmtfunction forOutput[#522]reason()method forTemplateErrorto access underlying reason,this replaces original direct
.reasonaccess.TemplateError'sreasonfield is depreacted willbe removed in future.
matklad/once_cell (once_cell)
v1.21.4Compare Source
Fix unsoundness in
OnceCell::waitunder--features=parking_lot, #295.If thread A calls
wait, while thread B callsget_or_try_init(f), and, furthermore,fpanics,the
waitincorrectly returns and thread A observes uninitialized memory.Kudos to @meng-xu-cs for a nice find!
v1.21.3Compare Source
race: #284,#285.
v1.21.2Compare Source
race: #278.v1.21.1Compare Source
v1.21.0Compare Source
race: #273.OnceNonZereUsize::get_unchecked: #274.OnceBox::cloneandOnceBox::with_value: #275.v1.20.3Compare Source
v1.20.2Compare Source
portable_atomicfrom Cargo.lock if it is not, in fact, used: #267This is a work-around for this cargo bug: rust-lang/cargo#10801.
v1.20.1Compare Source
racemodule using justportable_atomic, withoutcritical_sectionand providebetter error messages on targets without atomic CAS instruction,
#265.
v1.20.0Compare Source
v1.19.0Compare Source
portable-atomicinstead ofatomic-polyfill, #251.v1.18.0Compare Source
MSRVis updated to 1.60.0 to take advantage ofdep:syntax for cargo features,removing "implementation details" from publicly visible surface.
v1.17.2Compare Source
Lazy::{force,deref}_mut(), #231.v1.17.1Compare Source
OnceRefimplementation compliant with strict provenance.v1.17.0Compare Source
race::OnceReffor storing a&'a T.rust-lang/regex (regex)
v1.12.3Compare Source
===================
This release excludes some unnecessary things from the archive published to
crates.io. Specifically, fuzzing data and various shell scripts are now
excluded. If you run into problems, please file an issue.
Improvements:
Switch from a Cargo
excludelist to anincludelist, and exclude someunnecessary stuff.
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.
v1.9.6Compare 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.
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.5Compare 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_staticorsimilar 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-automatathat require passingstate 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
OnceLockorlazy_staticoronce_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:
Fix a performance bug where high contention on a single regex led to massive
slow-downs.
v1.9.4Compare Source
==================
This is a patch release that fixes a bug where
RegexSet::is_match(..)couldincorrectly return false (even when
RegexSet::matches(..).matched_any()returns true).
Bug fixes:
Fix a bug where a prefilter was incorrectly configured for a
RegexSet.v1.9.3Compare 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:
Fix a bug with the reverse inner literal optimization reporting incorrect match
offsets.
v1.9.2Compare 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:
Fix a memory usage regression when using a
RegexSet.v1.9.1Compare 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:
Change the allocation strategy for the backtracker to be less aggressive.
v1.9.0Compare 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:
Captures::extractmethod for quickly accessing the substringsthat match each capture group in a regex.
R, which enables CRLF mode. This makes.match anyUnicode scalar value except for
\rand\n, and also makes(?m:^)and(?m:$)match after and before both\rand\n, respectively, but neverbetween a
\rand\n.RegexBuilder::line_terminatorwas added to further customize the lineterminator used by
(?m:^)and(?m:$)to be any arbitrary byte.stdCargo feature is now actually optional. That is, theregexcratecan be used without the standard library.
regex 1.9may make binary size and compile times even worse, anew experimental crate called
regex-litehas been published. It prioritizesbinary size and compile times over functionality (like Unicode) and
performance. It shares no code with the
regexcrate.New features:
One can opt into CRLF mode via the
Rflag.e.g.,
(?mR:$)matches just before\r\n.Multi-pattern searches with offsets can be done with
regex-automata 0.3.stdis now an optional feature.regexmay be used with onlyalloc.RegexBuilder::line_terminatorconfigures how(?m:^)and(?m:$)behave.Anchored search APIs are now available in
regex-automata 0.3.Add new
Captures::extractmethod for easier capture group access.Add
regex-litecrate with smaller binary sizes and faster compile times.Add
TryFromimplementations for theRegextype.Performance improvements:
Added a one-pass DFA engine for faster capture group matching.
Inner literals are now used to accelerate searches, e.g.,
\w+@​\w+will scanfor
@.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:
Fix matching bugs related to
\Band inconsistencies across internal engines.Fix matching bug with capture groups.
Fix matching bug with word boundaries.
Fix bug where some regexes like
(re)+were not equivalent to(re)(re)*.Fix matching bug inconsistency between NFA and DFA engines.
Fix matching bug where literal extraction got confused by
$.Add documentation to replacement routines about dealing with fallibility.
Use corpus rejection in fuzz testing.
v1.8.4Compare Source
==================
This is a patch release that fixes a bug where
(?-u:\B)was allowed inUnicode 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.8because the underlyingsyntactical error that prevented this regex from compiling was intentionally
removed. That's because
(?-u:\B)will be permitted in Unicode regexes inregex 1.9, but the matching engines will guarantee to never report matchoffsets that split a codepoint. When the underlying syntactical error was
removed, no code was added to ensure that
(?-u:\B)didn't compile in theregex 1.8transition release. This release,regex 1.8.4, adds that codesuch that
Regex::new(r"(?-u:\B)")returns to theregex <1.8behavior ofnot compiling. (A
bytes::Regexcan still of course compile it.)Bug fixes:
Fix a bug where
(?-u:\B)was allowed in Unicode regexes, and in turn couldlead to match offsets that split a codepoint in
&str.v1.8.3Compare 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:
Fix a bug where a match at every position is erroneously reported.
v1.8.2Compare 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 wrappedin 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:
Fix a bug where regex compilation with large counted repetitions could panic.
v1.8.1Compare Source
==================
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:
Fix a bug where a word boundary could interact with prefix literal
optimizations and lead to a false positive match.
v1.8.0Compare Source
==================
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:
aho-corasickto the recently released 1.0version.
regex-syntaxto the simultaneously released0.7version. The changes toregex-syntaxprincipally revolve around arewrite 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-automataintothis repository, and then changing the
regexcrate to be nothing but an APIshim 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:
Perm
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.