refactor: update error handling and splitting

[nicotsx]

Summary by CodeRabbit

• Refactor
  • Enhanced update functionality with improved components and utilities for handling software releases.
• New Features
  • Publicly exposed API client creation to enhance extensibility.
• Documentation
  • Added a new module for release management.

[coderabbitai]

Walkthrough

The recent changes focus on streamlining the update process and enriching API interactions. Key updates involve removing outdated dependencies, introducing new release management utilities, and enhancing API client configurations. A dedicated release module consolidates version control functions for improved software update handling.

Changes

File Path	Change Summary
src/commands/update.rs	Removed outdated dependencies and added new release management utilities.
src/utils/api.rs	Made create_client() public and configured user agent settings.
src/utils/mod.rs and src/utils/release.rs	Introduced a release module for centralized software update management.

🐰✨
Oh hark! A change, a shift, a tweak,
In code where bytes and logic speak.
New paths we pave, old ones we close,
With every line, our purpose grows.
Spin the wheel, update the tale,
In software seas, we set the sail! 🚀
🐰✨

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 505f072 and f910363.

Files selected for processing (5)

• src/commands/update.rs (4 hunks)
• src/utils/api.rs (1 hunks)
• src/utils/mod.rs (1 hunks)
• src/utils/release.rs (1 hunks)
• src/utils/tests/release.rs (1 hunks)

Files not reviewed due to errors (1)

• src/utils/tests/release.rs (no review received)

Files skipped from review as they are similar to previous changes (3)

• src/utils/api.rs
• src/utils/mod.rs
• src/utils/release.rs

Additional comments not posted (5)

src/commands/update.rs (5)

23-33: The error handling in the version fetching logic is well-implemented, providing clear user feedback in case of failures.

---

46-49: Good implementation of error handling when fetching all releases. The spinner's fail message and the subsequent clean-up with spin.finish() are appropriate.

---

59-65: The logic to find the specific release based on the wanted_version is clear and well-handled, including appropriate user feedback if the version is not found.

---

73-79: The error handling for the download operation is consistent with other parts of the code, using the spinner effectively to communicate success or failure.

---

125-125: The final output using ConsoleBox is a nice touch, providing a user-friendly summary of the update process. However, ensure that the information about the project being written in TypeScript is accurate as it might confuse users if the project is primarily in Rust.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Ensure that the function download_release_and_self_relace is correctly named. It seems to be a typo and should probably be download_release_and_self_replace.