feat: bump sqlx to 0.8.2

[edisontim]

Description

Bump's sqlx version to 0.8.2, needed to run a rust binary with shuttle

Summary by CodeRabbit

• New Features

  • Updated the sqlx library to version "0.8.2," enhancing database interaction capabilities.

• Bug Fixes

  • Improved compatibility with the updated sqlx version, potentially resolving previous issues related to database operations.

[coderabbitai]

Walkthrough

Ohayo, sensei! The recent changes in the pull request focus on updating the Cargo.toml file, specifically enhancing dependency management. The workspace resolver is now set to version "2", and while the list of workspace members remains unchanged, the sqlx dependency has been upgraded from version "0.7.2" to "0.8.2". Other dependencies are intact, ensuring the overall structure of the file is preserved.

Changes

File	Change Summary
Cargo.toml	Updated sqlx dependency version from "0.7.2" to "0.8.2"; workspace resolver set to version "2"; other dependencies unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant A as Cargo.toml
    participant B as sqlx Library
    A->>B: Update version to 0.8.2
    A->>A: Maintain workspace structure

Loading

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 97b679b and 015e78f.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

Cargo.toml (1)

194-194: Ohayo, sensei! The sqlx update looks good!

The change from version 0.7.2 to 0.8.2 for the sqlx dependency aligns with the PR objectives. This update should improve compatibility with the Shuttle platform as intended.

To ensure a smooth transition, please consider the following:

1. Check the sqlx changelog for any breaking changes or new features that might affect your project.
2. Verify that all sqlx-related code in your project is compatible with the new version.
3. Run your test suite to catch any potential issues early.

Would you like assistance in generating a script to search for sqlx usage in the project?

---

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.

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 69.80%. Comparing base (97b679b) to head (015e78f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2565      +/-   ##
==========================================
+ Coverage   69.76%   69.80%   +0.03%     
==========================================
  Files         400      400              
  Lines       51183    51183              
==========================================
+ Hits        35709    35727      +18     
+ Misses      15474    15456      -18     

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