Skip to content

Bump the crates group with 3 updates - #26

Merged
jbutton merged 1 commit into
mainfrom
dependabot/cargo/crates-9bd7c1fa72
Nov 15, 2026
Merged

jbutton merged 1 commit into
mainfrom
dependabot/cargo/crates-9bd7c1fa72

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 15, 2026

Copy link
Copy Markdown
Contributor

Bumps the crates group with 3 updates: fancy-regex, toml and yaml-rust2.

Updates fancy-regex from 0.14.0 to 0.20.2

Release notes

Sourced from fancy-regex's releases.

0.20.2

Added

Changed

Fixed

  • Fixed more cases where the optimizations made were unsound (#333)

0.20.1

Added

  • A new Expr::has_descendant_or_self method to easily traverse the Expr descendants to find an Expr matching a predicate. (#319)
  • Add a RegexOptionsBuilder::optimize / RegexBuilder::optimize flag to disable the expression-tree optimization pass (enabled by default), and rework it into two tiers: optimize() now takes an OptimizeOptions struct with a find_not_empty flag that skips only the KeepOut (\K) and trailing-lookahead rewrites, while the safe rewrites still apply — so find_not_empty patterns benefit from them instead of skipping the whole pass. The decision on whether to optimize is centralized on RegexOptions::should_optimize and forwarded to the prefilter helpers (start_bytes, required_bytes) so they analyze the same tree as the compile path. (#323)
  • Support control character escapes \cX and \C-X in Oniguruma mode, e.g. \ca matches \x01 and \c\\ matches \x1C, both inside and outside of character classes. Without Oniguruma mode they are still invalid escapes. (#320)

Changed

Fixed

  • Positive lookaheads are now atomic, as in Oniguruma and PCRE: once a lookahead has matched, a later failure no longer backtracks into it to try another way of matching it. For example (?=x|(x))\1x no longer matches xx. (#313)
  • A hard variable-length lookbehind no longer reuses the candidate start positions left behind by a previous lookbehind that matched (or by a negative lookbehind whose body matched), which gave wrong results such as (b*)(?<!\1)c matching abc, or hit the backtrack limit when a pattern had two such lookbehinds, like (a*)b(?<=\1b)(c*)d(?<=\2d). (#314)
  • A repetition with a minimum count whose body can match an empty string (e.g. (?:a|(?=b)){2,}) could stop before reaching the minimum when it ran again at a position its previous run had reached, for example inside a repeated lookahead: (?:(?=(?:a|(?=b)){2,})a){2} matched aa. (#312)
  • A {n,} repetition whose body can match an empty string ended as soon as an iteration matched empty, even below the minimum. When the first iteration matched empty, the last required one now still runs, so (?:(?=^)a*){2,}b matches aab. A body that reads a capture group it sets itself can match differently in the next iteration, so there all required iterations run, and ^(?:(?(1)a|())){3,}$ no longer matches an empty string. (#325)
  • A conditional whose condition fails no longer leaves its entry on the VM's explicit stack. Before, an enclosing atomic group or possessive repeat read that entry at its end and kept its backtrack branches: (z)?(?>a*(?(1)x))a matched "aaa". (#316)
  • A conditional whose true branch is a group of alternatives, such as (?(1)(?:a|b)), was parsed as (?(1)a|b), so b became the false branch. (#315)
  • Inline flags set inside a capturing, named, atomic, lookaround, conditional or absent group, like (a(?i)b)c, now end with the group. Before, they leaked to the rest of the pattern, so (a(?i)b)c matched aBC and (?x)G(o(?-x)o) g did not ignore the spaces after the group. Only (?:...) and (?flags:...) restored them. (#317)
  • In Oniguruma mode, {,} is now literal text, as in Oniguruma, instead of being parsed as {0,}. For example (?:ab){,} matches ab{,}. {,n} is still {0,n}, and without Oniguruma mode {,} is unchanged. (#321)
  • In Oniguruma mode, a ? after an interval with swapped limits, like a{3,2}?, is now another quantifier, as in Oniguruma, so it makes the possessive a{2,3} optional. Before, it made the repeat lazy, so a{3,2}? matched aa in aaa and didn't match an empty string. A ?, * or + after a repeated empty group, like in (?:)** or (?:){3,2}?, is now dropped along with it instead of failing to parse. (#322)
  • In Oniguruma mode, a ? after a fixed interval, like a{3}?, is now another quantifier, as in Oniguruma, so a{3}? means (?:a{3})?. Before, it made the repeat lazy, which doesn't change anything for a fixed count, so a{3}? didn't match aa and a{3}?? matched aaa instead of an empty string. a{3,3}? is still lazy, and without Oniguruma mode a{3}? is unchanged.
  • A backref or conditional inside the group it refers to now sees the group's previous capture, as in PCRE and Perl. Before, it saw the new start of the group with the end of its previous capture, so (?:(\1|a)b){2} panicked on abab and ^((?(1)b|a))$ matched b but not a. (#328)

0.20.0

Added

  • Add RegexOptionsBuilder::build_delegate_prefilter to disable building the prefilter (#282)
  • Add RegexOptionsBuilder::start_bytes that returns the first bytes that can match a pattern so you can build your own prefilter (#282)
  • Add RegexOptionsBuilder::required_bytes that returns the required bytes for a pattern to match (#287)
  • Add RegexOptionsBuilder::max_prog_size / RegexBuilder::max_prog_size to cap the number of VM instructions emitted while compiling. Subroutine calls are inlined at compile time, so a self- or mutually-recursive pattern can expand without bound even while the recursion-depth cap is respected; this bounds the emitted instruction vector instead. Exceeding the cap returns CompileError::PatternTooComplex. Disabled by default. (#298)
  • Implement support for variable length hard lookbehinds, by seeking backwards to candidate match start positions and then matching forward as usual. The reverse DFA honours delegate_size_limit and delegate_dfa_size_limit. (#286, #309)
  • Add RegexOptionsBuilder::delegate_dfa_skip_cache_capacity_check / RegexBuilder::delegate_dfa_skip_cache_capacity_check, enabled by default. Setting it to false makes the reverse DFA of a variable-length lookbehind strictly honour delegate_dfa_size_limit, so a too-small limit becomes a compile error. (#309)
  • Add ByteSet::is_subset to test whether one byte set is a subset of another. (#289)

Changed

  • If a lookbehind consists of an Alt containing only easy expressions and at least 4 branches (and no capture groups), compile it as a variable lookbehind (if the feature is enabled) instead of trying every branch as its own const-size lookbehind. One reverse-DFA delegate over the whole alternation is much cheaper per attempt, and grants a perf boost. (#285)
  • Word boundaries (\b, \B, \<, \>) are no longer marked hard outside a lookbehind. regex-automata supports them, so a pattern like \b(?:foo|bar|baz)\b now compiles to a single delegated engine instead of one branch per alternative — previously it grew linearly with the number of alternatives. They remain hard inside a lookbehind, since regex-automata's reverse DFA can't run a variable-length lookbehind on unicode haystacks. The half-boundary variants (\<, \>) and \Z are still always hard. (#311)
  • The parser now tracks every capture group declared with the same name; Regex::capture_names reports the name for each of them, and named backrefs resolve to the last group with that name (#177)

Fixed

  • The reverse lazy DFA built for a variable-length lookbehind failed to compile when it needed a larger cache capacity than the configured delegate_dfa_size_limit (or the default of 2 MiB); for example (?<=\p{L}{99,100})x failed to compile with default settings. The capacity is now rounded up to the minimum required. Ordinary delegates were not affected because the meta engine falls back to another engine when the lazy DFA cannot be built. (#309)
  • delegate_dfa_size_limit now sets the lazy DFA cache capacity (hybrid_cache_capacity) as documented, instead of the fully compiled DFA size limit. It had been forwarded to the wrong regex-automata option since the switch from the regex crate. (#307)
  • Fix bug with literal bytes being used in unicode mode unexpectedly: in Unicode mode, \xHH escapes above 0x7F now match the Unicode codepoint (as UTF-8 bytes) instead of the raw byte, so e.g. \xFF matches ÿ rather than the byte 0xFF. In bytes modes the raw byte is matched as before. (#292)
  • Fix case-insensitive prefilter computation for non-ASCII class ranges that fold to characters with different lead bytes (e.g. (?i)[à-ÿ]), which previously could miss candidate start positions. (#296)
  • Fix ^ / $ and their multi-line variants matching at the start/end of arbitrary-byte haystacks in Ascii and UnicodeBytes bytes modes, where the match position was not a UTF-8 codepoint boundary. (#300)
  • Fix seek optimization dropping matches when conditionals had empty branches, e.g. (a)?b(?(1)c) no longer fails to match b. (#304)
  • Fix hard variable-length lookbehind reverse DFA ignoring the caller's Unicode and bytes-mode settings, giving wrong results in non-Unicode bytes modes (e.g. (?<=(\w+)\1)x on ééx). (#310)

0.19.2

Added

  • Add a leftmost_longest feature (off by default) that adds a method to the RegexBuilder/RegexOptionsBuilder for building a VM which would operate in leftmost-longest match mode instead of the regular leftmost-first mode. Useful for POSIX compliance. (#281)

... (truncated)

Changelog

Sourced from fancy-regex's changelog.

[0.20.2] - 2026-11-11

Added

Changed

Fixed

  • Fixed more cases where the optimizations made were unsound (#333)

[0.20.1] - 2026-11-09

Added

  • A new Expr::has_descendant_or_self method to easily traverse the Expr descendants to find an Expr matching a predicate. (#319)
  • Add a RegexOptionsBuilder::optimize / RegexBuilder::optimize flag to disable the expression-tree optimization pass (enabled by default), and rework it into two tiers: optimize() now takes an OptimizeOptions struct with a find_not_empty flag that skips only the KeepOut (\K) and trailing-lookahead rewrites, while the safe rewrites still apply — so find_not_empty patterns benefit from them instead of skipping the whole pass. The decision on whether to optimize is centralized on RegexOptions::should_optimize and forwarded to the prefilter helpers (start_bytes, required_bytes) so they analyze the same tree as the compile path. (#323)
  • Support control character escapes \cX and \C-X in Oniguruma mode, e.g. \ca matches \x01 and \c\\ matches \x1C, both inside and outside of character classes. Without Oniguruma mode they are still invalid escapes. (#320)

Changed

Fixed

  • Positive lookaheads are now atomic, as in Oniguruma and PCRE: once a lookahead has matched, a later failure no longer backtracks into it to try another way of matching it. For example (?=x|(x))\1x no longer matches xx. (#313)
  • A hard variable-length lookbehind no longer reuses the candidate start positions left behind by a previous lookbehind that matched (or by a negative lookbehind whose body matched), which gave wrong results such as (b*)(?<!\1)c matching abc, or hit the backtrack limit when a pattern had two such lookbehinds, like (a*)b(?<=\1b)(c*)d(?<=\2d). (#314)
  • A repetition with a minimum count whose body can match an empty string (e.g. (?:a|(?=b)){2,}) could stop before reaching the minimum when it ran again at a position its previous run had reached, for example inside a repeated lookahead: (?:(?=(?:a|(?=b)){2,})a){2} matched aa. (#312)
  • A {n,} repetition whose body can match an empty string ended as soon as an iteration matched empty, even below the minimum. When the first iteration matched empty, the last required one now still runs, so (?:(?=^)a*){2,}b matches aab. A body that reads a capture group it sets itself can match differently in the next iteration, so there all required iterations run, and ^(?:(?(1)a|())){3,}$ no longer matches an empty string. (#325)
  • A conditional whose condition fails no longer leaves its entry on the VM's explicit stack. Before, an enclosing atomic group or possessive repeat read that entry at its end and kept its backtrack branches: (z)?(?>a*(?(1)x))a matched "aaa". (#316)
  • A conditional whose true branch is a group of alternatives, such as (?(1)(?:a|b)), was parsed as (?(1)a|b), so b became the false branch. (#315)
  • Inline flags set inside a capturing, named, atomic, lookaround, conditional or absent group, like (a(?i)b)c, now end with the group. Before, they leaked to the rest of the pattern, so (a(?i)b)c matched aBC and (?x)G(o(?-x)o) g did not ignore the spaces after the group. Only (?:...) and (?flags:...) restored them. (#317)
  • In Oniguruma mode, {,} is now literal text, as in Oniguruma, instead of being parsed as {0,}. For example (?:ab){,} matches ab{,}. {,n} is still {0,n}, and without Oniguruma mode {,} is unchanged. (#321)
  • In Oniguruma mode, a ? after an interval with swapped limits, like a{3,2}?, is now another quantifier, as in Oniguruma, so it makes the possessive a{2,3} optional. Before, it made the repeat lazy, so a{3,2}? matched aa in aaa and didn't match an empty string. A ?, * or + after a repeated empty group, like in (?:)** or (?:){3,2}?, is now dropped along with it instead of failing to parse. (#322)
  • In Oniguruma mode, a ? after a fixed interval, like a{3}?, is now another quantifier, as in Oniguruma, so a{3}? means (?:a{3})?. Before, it made the repeat lazy, which doesn't change anything for a fixed count, so a{3}? didn't match aa and a{3}?? matched aaa instead of an empty string. a{3,3}? is still lazy, and without Oniguruma mode a{3}? is unchanged.
  • A backref or conditional inside the group it refers to now sees the group's previous capture, as in PCRE and Perl. Before, it saw the new start of the group with the end of its previous capture, so (?:(\1|a)b){2} panicked on abab and ^((?(1)b|a))$ matched b but not a. (#328)

[0.20.0] - 2026-10-24

Added

  • Add RegexOptionsBuilder::build_delegate_prefilter to disable building the prefilter (#282)
  • Add RegexOptionsBuilder::start_bytes that returns the first bytes that can match a pattern so you can build your own prefilter (#282)
  • Add RegexOptionsBuilder::required_bytes that returns the required bytes for a pattern to match (#287)
  • Add RegexOptionsBuilder::max_prog_size / RegexBuilder::max_prog_size to cap the number of VM instructions emitted while compiling. Subroutine calls are inlined at compile time, so a self- or mutually-recursive pattern can expand without bound even while the recursion-depth cap is respected; this bounds the emitted instruction vector instead. Exceeding the cap returns CompileError::PatternTooComplex. Disabled by default. (#298)
  • Implement support for variable length hard lookbehinds, by seeking backwards to candidate match start positions and then matching forward as usual. The reverse DFA honours delegate_size_limit and delegate_dfa_size_limit. (#286, #309)
  • Add RegexOptionsBuilder::delegate_dfa_skip_cache_capacity_check / RegexBuilder::delegate_dfa_skip_cache_capacity_check, enabled by default. Setting it to false makes the reverse DFA of a variable-length lookbehind strictly honour delegate_dfa_size_limit, so a too-small limit becomes a compile error. (#309)
  • Add ByteSet::is_subset to test whether one byte set is a subset of another. (#289)

Changed

  • If a lookbehind consists of an Alt containing only easy expressions and at least 4 branches (and no capture groups), compile it as a variable lookbehind (if the feature is enabled) instead of trying every branch as its own const-size lookbehind. One reverse-DFA delegate over the whole alternation is much cheaper per attempt, and grants a perf boost. (#285)
  • Word boundaries (\b, \B, \<, \>) are no longer marked hard outside a lookbehind. regex-automata supports them, so a pattern like \b(?:foo|bar|baz)\b now compiles to a single delegated engine instead of one branch per alternative — previously it grew linearly with the number of alternatives. They remain hard inside a lookbehind, since regex-automata's reverse DFA can't run a variable-length lookbehind on unicode haystacks. The half-boundary variants and \Z are still always hard. (#311)
  • The parser now tracks every capture group declared with the same name; Regex::capture_names reports the name for each of them, and named backrefs resolve to the last group with that name (#177)

Fixed

  • The reverse lazy DFA built for a variable-length lookbehind failed to compile when it needed a larger cache capacity than the configured delegate_dfa_size_limit (or the default of 2 MiB); for example (?<=\p{L}{99,100})x failed to compile with default settings. The capacity is now rounded up to the minimum required. Ordinary delegates were not affected because the meta engine falls back to another engine when the lazy DFA cannot be built. (#309)
  • delegate_dfa_size_limit now sets the lazy DFA cache capacity (hybrid_cache_capacity) as documented, instead of the fully compiled DFA size limit. It had been forwarded to the wrong regex-automata option since the switch from the regex crate. (#307)
  • Fix bug with literal bytes being used in unicode mode unexpectedly: in Unicode mode, \xHH escapes above 0x7F now match the Unicode codepoint (as UTF-8 bytes) instead of the raw byte, so e.g. \xFF matches ÿ rather than the byte 0xFF. In bytes modes the raw byte is matched as before. (#292)
  • Fix case-insensitive prefilter computation for non-ASCII class ranges that fold to characters with different lead bytes (e.g. (?i)[à-ÿ]), which previously could miss candidate start positions. (#296)
  • Fix ^ / $ and their multi-line variants matching at the start/end of arbitrary-byte haystacks in Ascii and UnicodeBytes bytes modes, where the match position was not a UTF-8 codepoint boundary. (#300)
  • Fix seek optimization dropping matches when conditionals had empty branches, e.g. (a)?b(?(1)c) no longer fails to match b. (#304)
  • Fix hard variable-length lookbehind reverse DFA ignoring the caller's Unicode and bytes-mode settings, giving wrong results in non-Unicode bytes modes (e.g. (?<=(\w+)\1)x on ééx). (#310)

[0.19.2] - 2026-09-13

Added

  • Add a leftmost_longest feature (off by default) that adds a method to the RegexBuilder/RegexOptionsBuilder for building a VM which would operate in leftmost-longest match mode instead of the regular leftmost-first mode. Useful for POSIX compliance. (#281)

... (truncated)

Commits
  • 5b33048 Version 0.20.2
  • 4cd67a7 Merge pull request #333 from fancy-regex/fix_ambiguous_quantifier_optimization
  • c5354e1 Add changelog entry
  • e9d3ac6 Expand optimize differential test cases to cover *, {2}, and {2,50} quantifiers
  • 9728425 Add differential test helper proving optimized regex matches unoptimized
  • dd589f7 Fix ambiguous concat repeat optimization widening bounded edges
  • a460c32 Version 0.20.1
  • 6832ab0 improve build_seek_pattern doc comments
  • 5df1aaa Rename misleading contains_word_boundary variable
  • 92e724e fix clippy warning
  • Additional commits viewable in compare view

Updates toml from 0.9.12+spec-1.1.0 to 1.2.1+spec-1.1.0

Commits

Updates yaml-rust2 from 0.10.4 to 0.13.0

Changelog

Sourced from yaml-rust2's changelog.

v0.13.0

Changes:

  • (#82) encoding_rs was pinned to versions prior to v0.8.40 to maintain the current MSRV.

Development:

  • Applied clippy fixes.

v0.12.0

Changes:

  • The minimum supported Rust version is now v1.85.0.
  • hashlink was upgraded to v0.12.1.
  • quickcheck (dev-only dependency) was upgraded to v1.1.0.
  • toml (dev-only dependency) was upgraded to v1.1.4.
  • (#79) corrected the documentation for Marker::index.

v0.11.1

Changes:

  • (#78) Fix parsing short YAML documents to avoid infinite loops.

v0.11.0

Changes:

  • The actions/checkout github actions dependency was updated.
  • The hashlink dependency was updated to v0.11.
Commits
  • e120694 yaml-rust2 v0.13.0
  • 3656505 cargo: pin encoding_rs to versions < 0.8.40 to maintain MSRV
  • 8c25872 garden: validate MSRV for the encoding feature flag
  • 4212204 garden: add "publish" command
  • 461e383 chore(deps): Update Rust crate libtest-mimic to v0.8.2 (#80)
  • e1741ae tools: apply clippy fixes
  • c015b50 CHANGELOG: reformat for readability
  • 3a06469 CHANGELOG: issue typofix
  • 0ed0fc7 yaml-rust v0.12.0
  • 0534dad scanner: correct the docstring that referenced chars
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the crates group with 3 updates: [fancy-regex](https://github.com/fancy-regex/fancy-regex), [toml](https://github.com/toml-rs/toml) and [yaml-rust2](https://github.com/Ethiraric/yaml-rust2).


Updates `fancy-regex` from 0.14.0 to 0.20.2
- [Release notes](https://github.com/fancy-regex/fancy-regex/releases)
- [Changelog](https://github.com/fancy-regex/fancy-regex/blob/main/CHANGELOG.md)
- [Commits](fancy-regex/fancy-regex@0.14.0...0.20.2)

Updates `toml` from 0.9.12+spec-1.1.0 to 1.2.1+spec-1.1.0
- [Commits](toml-rs/toml@toml-v0.9.12...toml-v1.2.1)

Updates `yaml-rust2` from 0.10.4 to 0.13.0
- [Release notes](https://github.com/Ethiraric/yaml-rust2/releases)
- [Changelog](https://github.com/Ethiraric/yaml-rust2/blob/master/CHANGELOG.md)
- [Commits](Ethiraric/yaml-rust2@v0.10.4...v0.13.0)

---
updated-dependencies:
- dependency-name: fancy-regex
  dependency-version: 0.20.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: crates
- dependency-name: toml
  dependency-version: 1.2.1+spec-1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: crates
- dependency-name: yaml-rust2
  dependency-version: 0.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: crates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 15, 2026
@jbutton
jbutton merged commit e5bc7ee into main Nov 15, 2026
4 checks passed
@dependabot
dependabot Bot deleted the dependabot/cargo/crates-9bd7c1fa72 branch November 15, 2026 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant