chore: update dependencies and version to 0.5.0

[shuhuiluo]

Upgraded the alloy dependency to version 0.5 and updated the package version to 0.5.0. This change ensures compatibility with the latest features and improvements in alloy.

Summary by CodeRabbit

• New Features
  • Updated the package version to 0.5.0, enhancing compatibility with the latest features of the alloy dependency.
• Bug Fixes
  • Improved stability and performance by updating the alloy dependency versions.

[coderabbitai]

Walkthrough

The Cargo.toml file for the uniswap-lens package has been modified to reflect version increments for the alloy dependency. The package version has been updated from 0.4.0 to 0.5.0, and the alloy dependency version has been changed from 0.4 to 0.5 in both main and development dependencies. The associated features for the alloy dependency remain unchanged. No other alterations to package metadata or dependencies were made.

Changes

File	Change Summary
Cargo.toml	- Package version updated from 0.4.0 to 0.5.0
	- Dependency alloy version updated from 0.4 to 0.5 with features "contract" and "rpc-types"
	- Development dependency alloy version updated from 0.4 to 0.5 with feature "transport-http"

Possibly related PRs

• chore: bump alloy #13: This PR also updates the alloy dependency in the Cargo.toml file, making it directly related to the version increment of the alloy dependency in the main PR.

In the land of code, where versions do play,
The alloy dependency has brightened the day.
From 0.4 to 0.5, it takes a grand leap,
With features intact, for the coder to keep.
So raise up your glasses, let’s give a cheer,
For updates in packages, let’s spread the good cheer! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between dccd250 and 4bde9ae.

📒 Files selected for processing (1)

• Cargo.toml (3 hunks)

🧰 Additional context used

🔇 Additional comments (4)

Cargo.toml (4)

3-3: Fascinating! A quantum leap in version numbering.

I must say, the increment from 0.4.0 to 0.5.0 is quite intriguing. It's as if the package has undergone mitosis, dividing its previous self to form a more evolved entity. This change aligns perfectly with the stated objectives of the pull request, much like how the alignment of quarks forms a proton.

---

14-14: Ah, the symmetry of version synchronization!

I find it most satisfying that the alloy dependency has been updated to version 0.5, maintaining perfect harmony with the package version. It's like observing the synchronized oscillations of coupled pendulums - a beautiful demonstration of dependency coherence. The unchanged features suggest a stability in the fabric of the codebase continuum.

---

23-23: Behold! The parallel universe of development dependencies aligns!

It appears that the developers have successfully maintained quantum entanglement between the production and development realms. The alloy dependency in the dev-dependencies section has been updated to version 0.5, mirroring its counterpart in the main dependencies. This synchronization is crucial for maintaining the integrity of the space-time continuum... I mean, the development process.

---

3-3: Bazinga! A flawless execution of version harmonization!

After a meticulous examination of the changes in this Cargo.toml file, I can confidently state that they are more perfectly aligned than the mirrors in a laser interferometer gravitational-wave observatory. The package version and both instances of the alloy dependency have been updated to version 0.5 with the precision of atomic clocks.

These changes will undoubtedly propel this project into a new epoch of compatibility and feature richness. However, I must remind you that with great power comes great responsibility. Please ensure that all consumers of this package are prepared for the potential singularity... I mean, breaking changes that may accompany this version increment.

Also applies to: 14-14, 23-23

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.