chore(deps): bump regex-automata from 0.4.11 to 0.4.12 in the patch-versions group #6160
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=80&v=4){kind=small}
Bumps the patch-versions group with 1 update: [regex-automata](https://github.com/rust-lang/regex). Updates `regex-automata` from 0.4.11 to 0.4.12 - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](rust-lang/regex@regex-automata-0.4.11...regex-automata-0.4.12) --- updated-dependencies: - dependency-name: regex-automata dependency-version: 0.4.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-versions ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
dependabot
bot
added
the
dependencies
WalkthroughUpdated two workspace dependency versions in Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
Cargo.toml(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: Build forest binaries on Linux AMD64
- GitHub Check: Build Ubuntu
- GitHub Check: cargo-publish-dry-run
- GitHub Check: Build MacOS
- GitHub Check: tests-release
- GitHub Check: tests
- GitHub Check: All lint checks
🔇 Additional comments (1)
Cargo.toml (1)
257-257: regex-automata version verified Cargo.toml’s caret constraint "0.4" and Cargo.lock resolution at 0.4.12 confirm the bump.
| educe = { version = "0.6.0", features = ["Debug"], default-features = false } | ||
| enumflags2 = "0.7" | ||
| ethereum-types = { version = "0.15", features = ["ethbloom"] } | ||
| ethereum-types = { version = "0.16", features = ["ethbloom"] } |
There was a problem hiding this comment.
🧩 Analysis chain
ethereum-types 0.16: sanity-check features and MSRV
Looks fine; please verify “ethbloom” feature still exists and there are no breaking API/MSRV bumps impacting us.
🌐 Web query:
ethereum-types 0.16 changelog breaking changes and feature list (is `ethbloom` still present?)
💡 Result:
Short answer: I can't find an ethereum-types 0.16 release. The latest published version is 0.15.1 (2024-09-12). In 0.15.1 ethbloom exists as a feature (it was made optional in 0.14.0) and the crate still exposes an "ethbloom" feature (enabled by default in 0.15.1). [1][2]
Sources
- ethereum-types changelog (shows 0.15.1 and that ethbloom was made optional in 0.14.0). [1]
- ethereum-types 0.15.1 features page (lists ethbloom as a feature, default-enabled). [2]
Invalid ethereum-types version bump
Cargo.toml:67 sets ethereum-types = "0.16", but no such release exists on crates.io; update to a valid version (e.g., 0.15.1).
🤖 Prompt for AI Agents
In Cargo.toml around line 67, the dependency line sets ethereum-types = "0.16"
which does not exist on crates.io; change the version to a valid release (for
example "0.15.1") and then run cargo update -p ethereum-types (or cargo update)
to refresh Cargo.lock so the lockfile matches the updated dependency.
| jsonrpsee = { version = "0.26", features = ["server", "ws-client", "http-client", "macros"] } | ||
| jsonwebtoken = { version = "10", features = ["rust_crypto"] } | ||
| keccak-hash = "0.11" | ||
| keccak-hash = "0.12" |
There was a problem hiding this comment.
🧩 Analysis chain
keccak-hash 0.12: confirm API compatibility
Approve, but double‑check for API or trait changes (e.g., keccak_256 signatures) and MSRV bumps.
🌐 Web query:
keccak-hash crate 0.12 release notes or changelog; any breaking changes from 0.11?
💡 Result:
I couldn't find a keccak-hash 0.12 release — the latest published release is 0.11.0 (Sep 11, 2024). No 0.12 changelog or release notes are available, so there are no documented breaking changes from 0.11 to 0.12. [1][2]
Sources:
- Libraries.io keccak-hash releases (shows 0.11.0 as latest). [1]
- docs.rs / crate page for keccak-hash (0.11.0). [2]
Cargo.toml: invalid keccak-hash version
keccak-hash = "0.12" references a non-existent release (latest is 0.11.0); update to a published version.
🤖 Prompt for AI Agents
In Cargo.toml at line 117, the dependency keccak-hash is pinned to a
non-existent version "0.12"; update that entry to a published release (for
example "0.11" or "0.11.0") so Cargo can resolve the crate, then run cargo
update / cargo build to verify resolution and adjust any breaking changes if
necessary.
2 participants
Bumps the patch-versions group with 1 update: regex-automata.
Updates
regex-automatafrom 0.4.11 to 0.4.12Commits
459dbberegex-automata-0.4.12610bf2dregex-syntax-0.8.77dbb384changelog: 1.12.0bd345d7automata: fix broken universal start states with sparse DFA72618c6regex: addCaptures::as_matchmethod821a8earegex[-lite]: inline format arguments81042ecautomata: inline format arguments5070f75syntax: inline format arguments91a92a9capi: inline format argumentse699918capi: update to Rust 2021Dependabot 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 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 conditionsSummary by CodeRabbit