Repository navigation
chore(deps): bump fancy-regex from 0.19.2 to 0.20.0 in /crates/bashkit/fuzz in the fuzz-dependencies group - #2806
Conversation
Bumps the fuzz-dependencies group in /crates/bashkit/fuzz with 1 update: [fancy-regex](https://github.com/fancy-regex/fancy-regex). Updates `fancy-regex` from 0.19.2 to 0.20.0 - [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.19.2...0.20.0) --- updated-dependencies: - dependency-name: fancy-regex dependency-version: 0.20.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: fuzz-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 9f2495b | Commit Preview URL Branch Preview URL |
Nov 02 2026, 09:50 AM |
…2813) Supersedes #2806, which bumped the workspace `fancy-regex` requirement in the root Cargo.toml but refreshed only crates/bashkit/fuzz/Cargo.lock, because the fuzz-dependencies group is scoped to that directory while the dependency lives in the workspace root. The root and examples/hyperlight lockfiles stayed at 0.19.2, so every --locked job failed with "cannot update the lock file ... because --locked was passed". Bump the requirement and all three lockfiles that resolve fancy-regex together. The unrelated transitive 0.17.0 copy in the root lockfile is untouched. Retarget the cargo-vet exemption from 0.19.2 to 0.20.0, and record that REGEX_DFA_SIZE_LIMIT now means different things to its two consumers. 0.20.0 carries three upstream changes that land on code paths this repo cares about, since grep, sed, rg and jq all compile on this engine under TM-DOS-025 backtracking bounds: - `delegate_dfa_size_limit` now sets the lazy-DFA cache capacity rather than a compiled-DFA size cap, and `delegate_dfa_skip_cache_capacity_check` is on by default, so the 1 MB value degrades instead of hard-erroring when undersized. REGEX_SIZE_LIMIT and FANCY_BACKTRACK_LIMIT still bound compilation and backtracking, so TM-DOS-025 does not rest on this knob. - In Unicode mode `\xHH` above 0x7F now matches the codepoint. - `\b`, `\B`, `\<` and `\>` are no longer hard outside lookbehinds. No call sites changed; the builder methods in use are unchanged in 0.20.0. Validated locally with 7091 tests passing across the workspace slice, clippy clean at -D warnings, cargo fmt clean, cargo vet --locked succeeding, and all five backtracking-limit tests green. All 54 PR checks pass.
|
Superseded by #2813, now merged: This PR could not go green on its own. The #2813 bumps the requirement and all three lockfiles together, retargets the Closing as redundant. Generated by Claude Code |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the fuzz-dependencies group in /crates/bashkit/fuzz with 1 update: fancy-regex.
Updates
fancy-regexfrom 0.19.2 to 0.20.0Release notes
Sourced from fancy-regex's releases.
Changelog
Sourced from fancy-regex's changelog.
Commits
031e5e5Version 0.20.0735c50adocs: add missing CHANGELOG entries for 0.19.2..main5973d40Merge pull request #311 from fancy-regex/easy_wordboundary_except_in_lookbehind647646aMake VM word-boundary assertions respect unicode_moded97e33cSerialize half word boundaries correct inExpr::to_str466bc65Add tests for word-boundary hardness outside a lookbehind5ba2a98Splitin_lookaroundin the analyzer intoin_lookahead/in_lookbehindwit...7a0ff5dAdd word-boundary perf benchmark comparing hard vs delegated word boundariesef97e6dimprove word boundary seek behavior03dd46aadd unicode word boundary testsDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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 conditionsNeed help on this PR? Tag
@codesmith-botwith what you need.