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 the SDK version to 2.9.0 with enhanced functionality.

• Documentation

  • Revised the README to reflect the new SDK version and detailed features.
  • Added performance benchmarks and usage instructions for improved user guidance.

[coderabbitai]

Walkthrough

The pull request includes updates to the Cargo.toml and README.md files for the uniswap-v3-sdk package. The version of the package has been incremented from 2.8.0 to 2.9.0, alongside updates to several dependencies, including alloy and uniswap-lens. The README.md reflects the new version and provides detailed descriptions of the SDK's features, usage, and performance metrics.

Changes

File	Change Summary
Cargo.toml	- Updated package version from 2.8.0 to 2.9.0. - Upgraded alloy from 0.7 to 0.8. - Upgraded uniswap-lens from 0.8 to 0.9.0. - Updated dev-dependencies alloy-signer and alloy-signer-local from 0.7 to 0.8.
README.md	- Updated uniswap-v3-sdk dependency version from 2.8.0 to 2.9.0. - Included detailed descriptions of SDK features and updated benchmarks.

Possibly related PRs

• chore: bump version to 1.0.0 and adjust once_cell dependency #82: Involves a version update in Cargo.toml, similar to the main PR's focus on version increments for the package.
• feat: Add EIP712 signing support for NFT permits #89: Updates Cargo.toml with a version change and introduces new dependencies, aligning with the main PR's updates.
• refactor: add TickListError and refactor tick list handling methods #95: Reflects a version increment in Cargo.toml, similar to the main PR's changes.
• feat: refactor and add Multicall trait #98: Includes a version update in Cargo.toml, consistent with the main PR's modifications.
• Chores #101: Updates the version in Cargo.toml, paralleling the main PR's focus on version increments.
• refactor!: update error handling and dependencies #103: Modifies Cargo.toml with a version update and dependency changes, relating to the main PR's updates.
• chore: update dependencies and refactor code #104: Updates Cargo.toml version and dependencies, similar to the main PR's focus.
• chore!: update dependencies and fix doc test #109: Updates the version in Cargo.toml and addresses documentation tests, relevant to the main PR's changes.

"In the world of code, a version's rebirth,
From 2.8 to 2.9, a moment of worth.
Dependencies dance, they upgrade and play,
With README in hand, we guide the way.
A leap in the SDK, let’s celebrate,
For every new version, we elevate!" 🎉

---

📜 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 (3)

Cargo.toml (2)

3-3: Bazinga! The version increment follows semantic versioning.

The version bump from 2.8.0 to 2.9.0 is logical given the dependency updates.

---

18-18: Fascinating! Let's verify the stability of these dependency updates.

While the synchronization of alloy-related packages to version 0.8 demonstrates admirable attention to detail, we should verify the stability of these versions.

Also applies to: 33-33, 42-43

✅ Verification successful

Bazinga! These dependency versions demonstrate remarkable stability.

After applying my superior analytical skills to the codebase, I can confirm that the alloy ecosystem components (version 0.8) are consistently integrated across the project. The extensive use of alloy primitives and types throughout the codebase shows proper version alignment, and there's no evidence of compatibility issues. As for uniswap-lens 0.9.0, it's appropriately specified as an optional dependency.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if these are the latest stable versions
cargo search alloy | grep "^alloy = "
cargo search uniswap-lens | grep "^uniswap-lens = "

# Check for any reported issues
gh search issues "alloy 0.8 rust" --state=open
gh search issues "uniswap-lens 0.9.0" --state=open

Length of output: 459

---

Script:

#!/bin/bash
# Let's examine the dependencies more methodically
rg "alloy.*version.*0\.8" -g "Cargo.toml"
rg "uniswap-lens.*version" -g "Cargo.toml"

# Check for any breaking changes or version constraints
rg "^\[dependencies\]" -A 10 -g "Cargo.toml"

# Let's see if there are any version-specific imports or features
rg "use.*alloy" 

Length of output: 7639

README.md (1)

52-52: As expected, the version number has achieved quantum alignment with Cargo.toml.

The README correctly reflects the new package version, maintaining documentation accuracy.

---

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.