chore(deps): bump regex from 1.5.4 to 1.6.0
Bumps regex from 1.5.4 to 1.6.0.
Changelog
Sourced from regex's changelog.
1.6.0 (2022-07-05)
This release principally includes an upgrade to Unicode 14.
New features:
- [FEATURE #832](rust-lang/regex#832): Clarify that
Captures::lenincludes all groups, not just matching groups.- [FEATURE #857](rust-lang/regex#857): Add an
ExactSizeIteratorimpl forSubCaptureMatches.- [FEATURE #861](rust-lang/regex#861): Improve
RegexSetdocumentation examples.- [FEATURE #877](rust-lang/regex#877): Upgrade to Unicode 14.
Bug fixes:
- [BUG #792](rust-lang/regex#792): Fix error message rendering bug.
1.5.6 (2022-05-20)
This release includes a few bug fixes, including a bug that produced incorrect matches when a non-greedy
?operator was used.
- [BUG #680](rust-lang/regex#680): Fixes a bug where
[[:alnum:][:^ascii:]]dropped[:alnum:]from the class.- [BUG #859](rust-lang/regex#859): Fixes a bug where
Hir::is_match_emptyreturnedfalsefor\b.- [BUG #862](rust-lang/regex#862): Fixes a bug where 'ab??' matches 'ab' instead of 'a' in 'ab'.
1.5.5 (2022-03-08)
This releases fixes a security bug in the regex compiler. This bug permits a vector for a denial-of-service attack in cases where the regex being compiled is untrusted. There are no known problems where the regex is itself trusted, including in cases of untrusted haystacks.
- SECURITY #GHSA-m5pq-gvj9-9vr8: Fixes a bug in the regex compiler where empty sub-expressions subverted the existing mitigations in place to enforce a size limit on compiled regexes. The Rust Security Response WG published an advisory about this: https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw
Commits
fc9ee6a1.6.08ddc8ecdeps: bump regex-syntax to 0.6.278c0eccdregex-syntax-0.6.27dee5c25changelog: 1.6.09ca3099regex: fix clippy lints up to rust 1.41.1de83828syntax: fix clippy lints up to rust 1.41.1b87cd88syntax: include only the start of the character class on error9d1478cdoc: fix typos7d21662doc: clarify Captures::len includes non-matching captures5e98788perf: use is_match_at instead of shortest_match_at- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)