Update alloy and related dependencies to 1.4.0

[0xh3rman]

Bump alloy-signer, alloy-signer-local, alloy-network, alloy-consensus, and alloy-ens to version 1.4.0. Also update serde_json to 1.0.149 and bigdecimal to 0.4.10 to keep dependencies current and compatible.

[semanticdiff-com]

Review changes with  

[gemini-code-assist]

Summary of Changes

Hello @0xh3rman, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on a comprehensive update of various alloy crates to their 1.4.0 release, ensuring the project benefits from the latest features, bug fixes, and performance enhancements. Alongside these core updates, other key dependencies such as serde_json, bigdecimal, and zmij have also been updated to maintain overall dependency health and compatibility within the project's ecosystem.

Highlights

• Alloy Dependencies Update: Multiple core alloy crates, including alloy-signer, alloy-signer-local, alloy-network, alloy-consensus, alloy-ens, alloy-consensus-any, alloy-eips, alloy-json-rpc, alloy-network-primitives, alloy-rpc-types-any, alloy-rpc-types-eth, alloy-serde, and alloy-tx-macros, have been updated to version 1.4.0.
• General Dependency Updates: The serde_json dependency has been bumped to 1.0.149 and bigdecimal to 0.4.10 to ensure compatibility and leverage the latest improvements.
• Minor Dependency Update: The zmij dependency has been upgraded from 0.1.8 to 1.0.13.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates several dependencies, including alloy-* crates to version 1.4.0, serde_json to 1.0.149, and bigdecimal to 0.4.10. The changes are straightforward dependency bumps. My main feedback is regarding the versioning of the alloy-* crates. To maintain consistency across the workspace, I've suggested updating them to 1.5.2, which is the latest version and matches other alloy-* crates already in use in the project. This will help prevent potential compatibility issues and ensures you are using the most up-to-date versions.