fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
regex	dependencies	minor	1.8.4 -> 1.9.1
serde (source)	dependencies	patch	1.0.164 -> 1.0.167
toml	dependencies	patch	0.7.5 -> 0.7.6

---

Release Notes

rust-lang/regex (regex)

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+@​\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.

serde-rs/serde (serde)

v1.0.167

Compare Source

• Add serialize and deserialize impls for RangeFrom and RangeTo (#​2471, thanks @​tbu-)

v1.0.166

Compare Source

• Add no-alloc category to crates.io metadata

v1.0.165

Compare Source

• Fix incorrect count of fields passed to tuple deserialization methods when using serde(skip_deserializing) attributes (#​2466, thanks @​Mingun)
• Fix -Zminimal-versions build

toml-rs/toml (toml)

v0.7.6

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

---

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

---

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

[pull-request-quantifier-deprecated]

This PR has 57 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Small
Size       : +34 -23
Percentile : 22.8%

Total files changed: 2

Change summary by file extension:
.lock : +31 -20
.toml : +3 -3

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.