chore: upgrade dependencies and bump version to 2.9.0

[shuhuiluo]

Updated various dependencies to their latest versions, including alloy, uniswap-lens, and alloy-signer, to maintain compatibility and improve functionality. Incremented the package version to reflect these updates.

Summary by CodeRabbit

• New Features

  • Updated package version to 2.9.0.
  • Enhanced dependencies, including alloy and uniswap-lens.

• Documentation

  • Updated the "Getting started" section in the README to reflect the new version 2.9.0.

[coderabbitai]

Walkthrough

The pull request introduces updates to the Cargo.toml and README.md files for the uniswap-v3-sdk package. The package version has been incremented from 2.8.0 to 2.9.0, along with updates to several dependencies including alloy, uniswap-lens, and development dependencies alloy-signer and alloy-signer-local. The README file reflects these version changes in the "Getting started" section, while maintaining its overall structure and content.

Changes

File	Change Summary
Cargo.toml	- Package version updated from 2.8.0 to 2.9.0 - Dependency alloy updated from 0.7 to 0.8 - Dependency uniswap-lens updated from 0.8 to 0.9.0 - Dev-dependencies alloy-signer and alloy-signer-local updated from 0.7 to 0.8
README.md	- Dependency version updated from 2.8.0 to 2.9.0 in the "Getting started" section

Possibly related PRs

• chore: upgrade dependencies and bump version to 2.9.0 #111: This PR is directly related as it also updates the Cargo.toml file, incrementing the package version from 2.8.0 to 2.9.0 and updating the same dependencies (alloy, uniswap-lens, alloy-signer) as in the main PR.

In the land of code, where versions do rise,
A leap from two-eight to two-nine is quite wise.
Dependencies dance, in a rhythmic delight,
With alloy and lens shining ever so bright.
Readme updates, a version to boast,
In the world of Uniswap, we now raise a toast! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 40e9623 and 735ba51.

📒 Files selected for processing (2)

• Cargo.toml (4 hunks)
• README.md (1 hunks)

🔇 Additional comments (4)

Cargo.toml (3)

3-3: Bazinga! The version bump follows semantic versioning principles.

The increment from 2.8.0 to 2.9.0 is appropriate for dependency updates.

---

33-33: The uniswap-lens upgrade appears logical.

The bump from 0.8 to 0.9.0 aligns with the overall dependency refresh strategy.

---

18-18: Fascinating! The alloy ecosystem dependencies are synchronized.

All alloy-related dependencies (alloy, alloy-signer, alloy-signer-local) have been consistently updated to version 0.8.

Also applies to: 42-43

✅ Verification successful

Bazinga! The hypothesis regarding alloy dependency synchronization has been empirically validated!

The experimental data conclusively demonstrates that all alloy-related dependencies (alloy, alloy-primitives, alloy-signer, alloy-signer-local, and alloy-sol-types) are indeed uniformly aligned at version 0.8, adhering to the fundamental principle of dependency consistency.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify if all alloy dependencies are on the same version
rg "alloy.*= \"0\." --no-filename | sort | uniq

Length of output: 215

README.md (1)

52-52: As expected, the documentation has been updated with surgical precision!

The example dependency version matches the package version in Cargo.toml.

---

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 generate docstrings to generate docstrings for this PR. (Experiment)
• @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.