-
Notifications
You must be signed in to change notification settings - Fork 5
Commit 4ed50d3
authored
chore(deps): Update compatible (dev) (#108)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [regex](https://redirect.github.com/rust-lang/regex) |
dev-dependencies | minor | `1.11.1` -> `1.12.2` |
| [snapbox](https://redirect.github.com/assert-rs/snapbox) |
dev-dependencies | patch | `0.6.21` -> `0.6.23` |
---
### Release Notes
<details>
<summary>rust-lang/regex (regex)</summary>
###
[`v1.12.2`](https://redirect.github.com/rust-lang/regex/blob/HEAD/CHANGELOG.md#1122-2025-10-13)
[Compare
Source](https://redirect.github.com/rust-lang/regex/compare/1.12.1...1.12.2)
\===================
This release fixes a `cargo doc` breakage on nightly when `--cfg docsrs`
is
enabled. This caused documentation to fail to build on docs.rs.
Bug fixes:
- [BUG
#​1305](https://redirect.github.com/rust-lang/regex/issues/1305):
Switches the `doc_auto_cfg` feature to `doc_cfg` on nightly for docs.rs
builds.
###
[`v1.12.1`](https://redirect.github.com/rust-lang/regex/blob/HEAD/CHANGELOG.md#1121-2025-10-10)
[Compare
Source](https://redirect.github.com/rust-lang/regex/compare/1.12.0...1.12.1)
\===================
This release makes a bug fix in the new `regex::Captures::get_match` API
introduced in `1.12.0`. There was an oversight with the lifetime
parameter
for the `Match` returned. This is technically a breaking change, but
given
that it was caught almost immediately and I've yanked the `1.12.0`
release,
I think this is fine.
###
[`v1.12.0`](https://redirect.github.com/rust-lang/regex/blob/HEAD/CHANGELOG.md#1120-2025-10-10)
[Compare
Source](https://redirect.github.com/rust-lang/regex/compare/1.11.3...1.12.0)
\===================
This release contains a smattering of bug fixes, a fix for excessive
memory
consumption in some cases and a new `regex::Captures::get_match` API.
Improvements:
- [FEATURE
#​1146](https://redirect.github.com/rust-lang/regex/issues/1146):
Add `Capture::get_match` for returning the overall match without
`unwrap()`.
Bug fixes:
- [BUG
#​1083](https://redirect.github.com/rust-lang/regex/issues/1083):
Fixes a panic in the lazy DFA (can only occur for especially large
regexes).
- [BUG
#​1116](https://redirect.github.com/rust-lang/regex/issues/1116):
Fixes a memory usage regression for large regexes (introduced in `regex
1.9`).
- [BUG
#​1195](https://redirect.github.com/rust-lang/regex/issues/1195):
Fix universal start states in sparse DFA.
- [BUG
#​1295](https://redirect.github.com/rust-lang/regex/pull/1295):
Fixes a panic when deserializing a corrupted dense DFA.
- [BUG
8f5d9479](https://redirect.github.com/rust-lang/regex/commit/8f5d9479d0f1da5726488a530d7fd66a73d05b80):
Make `regex_automata::meta::Regex::find` consistently return `None` when
`WhichCaptures::None` is used.
###
[`v1.11.3`](https://redirect.github.com/rust-lang/regex/blob/HEAD/CHANGELOG.md#1113-2025-09-25)
[Compare
Source](https://redirect.github.com/rust-lang/regex/compare/1.11.2...1.11.3)
\===================
This is a small patch release with an improvement in memory usage in
some
cases.
Improvements:
- [BUG
#​1297](https://redirect.github.com/rust-lang/regex/issues/1297):
Improve memory usage by trimming excess memory capacity in some spots.
###
[`v1.11.2`](https://redirect.github.com/rust-lang/regex/blob/HEAD/CHANGELOG.md#1112-2025-08-24)
[Compare
Source](https://redirect.github.com/rust-lang/regex/compare/1.11.1...1.11.2)
\===================
This is a new patch release of `regex` with some minor fixes. A larger
number
of typo or lint fix patches were merged. Also, we now finally recommend
using
`std::sync::LazyLock`.
Improvements:
- [BUG
#​1217](https://redirect.github.com/rust-lang/regex/issues/1217):
Switch recommendation from `once_cell` to `std::sync::LazyLock`.
- [BUG
#​1225](https://redirect.github.com/rust-lang/regex/issues/1225):
Add `DFA::set_prefilter` to `regex-automata`.
Bug fixes:
- [BUG
#​1165](https://redirect.github.com/rust-lang/regex/pull/1150):
Remove `std` dependency from `perf-literal-multisubstring` crate
feature.
- [BUG
#​1165](https://redirect.github.com/rust-lang/regex/pull/1165):
Clarify the meaning of `(?R)$` in the documentation.
- [BUG
#​1281](https://redirect.github.com/rust-lang/regex/pull/1281):
Remove `fuzz/` and `record/` directories from published crate on
crates.io.
</details>
<details>
<summary>assert-rs/snapbox (snapbox)</summary>
###
[`v0.6.23`](https://redirect.github.com/assert-rs/snapbox/compare/snapbox-v0.6.22...snapbox-v0.6.23)
[Compare
Source](https://redirect.github.com/assert-rs/snapbox/compare/snapbox-v0.6.22...snapbox-v0.6.23)
###
[`v0.6.22`](https://redirect.github.com/assert-rs/snapbox/compare/snapbox-v0.6.21...snapbox-v0.6.22)
[Compare
Source](https://redirect.github.com/assert-rs/snapbox/compare/snapbox-v0.6.21...snapbox-v0.6.22)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "before 5am on the first day of the
month" (UTC), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/gitext-rs/git2-ext).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>1 parent e8799aa commit 4ed50d3Copy full SHA for 4ed50d3
File tree
Expand file treeCollapse file tree
1 file changed
+114
-20
lines changedOpen diff view settings
Filter options
Expand file treeCollapse file tree
1 file changed
+114
-20
lines changedOpen diff view settings
Collapse file
+114-20Lines changed: 114 additions & 20 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments