chore(deps): bump fancy-regex to 0.20.0 across all three lockfiles

Cargo.toml

@@ -62,7 +62,7 @@ rustls = { version = "0.23", default-features = false, features = ["std", "tls12
 # Regex
 regex = "1"
 regex-automata = { version = "0.4", default-features = false, features = ["std", "syntax", "hybrid", "unicode", "perf"] }
-fancy-regex = "0.19"
+fancy-regex = "0.20"
 
 # Date/Time
 # Important decision: `default-features = false` drops chrono's `wasmbind`,

crates/bashkit/src/builtins/search_common.rs

@@ -13,7 +13,14 @@ use crate::builtins::limits::RUNTIME_REGEX_CACHE_ENTRIES;
 /// Default compiled-regex size limit (1 MB).
 pub(crate) const REGEX_SIZE_LIMIT: usize = 1_000_000;
 
-/// Default DFA size limit (1 MB).
+/// Default DFA budget (1 MB).
+///
+/// Two engines read this constant and mean different things by it. For the
+/// `regex` crate it is `dfa_size_limit`, a cap on compiled DFA size. For
+/// fancy-regex it is `delegate_dfa_size_limit`, which since 0.20.0 sets the
+/// *lazy-DFA cache capacity* rather than a compiled-DFA size cap; 0.20.0 also
+/// enables `delegate_dfa_skip_cache_capacity_check` by default, so a value too
+/// small for a pattern degrades instead of failing to compile.
 pub(crate) const REGEX_DFA_SIZE_LIMIT: usize = 1_000_000;
 
 /// Backtracking step cap for the fancy-regex (PCRE / `grep -P`) engine.

supply-chain/config.toml

@@ -597,7 +597,7 @@ version = "0.17.0"
 criteria = "safe-to-deploy"
 
 [[exemptions.fancy-regex]]
-version = "0.19.2"
+version = "0.20.0"
 criteria = "safe-to-deploy"
 
 [[exemptions.fastbloom]]