chore(katana): use workspace dep

[kariy]

Summary by CodeRabbit

• Chores
  • Updated serde_json dependency to use workspace-level version management
  • Minor formatting improvements in dependency declarations

[coderabbitai]

Walkthrough

Ohayo, sensei! The pull request introduces a subtle yet meaningful change in the katana-provider package's Cargo.toml. The primary modification involves transitioning the serde_json dependency from a fixed version to a workspace-relative declaration. This shift allows for more centralized dependency management across the project workspace, potentially simplifying version control and ensuring consistency.

Changes

File	Change Summary
crates/katana/storage/provider/Cargo.toml	- Replaced serde_json = { version = "1.0.133" } with serde_json.workspace = true - Minor formatting adjustment in test-utils feature declaration

Possibly related PRs

• fix(katana): genesis deprecated declared classes in state updates #2893: Handles deprecated declared classes in state updates, which shares a similar theme of improving project structure and dependency management

Note: No sequence diagram is generated for this change as it primarily involves dependency configuration in the Cargo.toml file.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b5e45c3 and 2b3cfa7.

📒 Files selected for processing (1)

• crates/katana/storage/provider/Cargo.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: fmt

🔇 Additional comments (2)

crates/katana/storage/provider/Cargo.toml (2)

29-29: Ohayo! Nice workspace dependency transition, sensei!

The change to use workspace-level dependency management for serde_json aligns well with the PR objectives and helps maintain consistent versions across the workspace.

---

35-35: LGTM! Clean formatting, sensei!

The spacing adjustment in the test-utils feature declaration maintains consistent formatting.

---

🪧 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. (Beta)
• @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.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.83%. Comparing base (dd1ccce) to head (2b3cfa7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2895      +/-   ##
==========================================
+ Coverage   55.81%   55.83%   +0.01%     
==========================================
  Files         449      449              
  Lines       57697    57700       +3     
==========================================
+ Hits        32206    32219      +13     
+ Misses      25491    25481      -10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.