fix release

[ponderingdemocritus]

• fixes dojoup release

Summary by CodeRabbit

• New Features

  • Enhanced version recognition to support pre-release versions, including release candidates.

• Bug Fixes

  • Improved error handling for unsupported platforms and missing dependencies.

• Chores

  • Added checks for necessary tools (git, curl, cargo) to ensure smooth installations.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Ohayo, sensei! This pull request modifies the version normalization logic in the dojoup script's main function. It updates the regular expression to recognize version tags, now accommodating pre-release versions with an optional -rc.<number> suffix. Additionally, it includes checks for essential tools like git, curl, and cargo, ensuring they are available before installation. The overall control flow remains unchanged, maintaining error handling and the structure for downloading and installing binaries.

Changes

File Path	Change Summary
.../dojoup	Updated regex in main function for version normalization to include -rc.<number> suffix.
.../dojoup	Added checks for required tools (git, curl, cargo) before installation.
.../dojoup	Maintained overall control flow, error handling, and structure for binary installation.

Possibly related PRs

• Prepare release: v1.0.0-alpha.19 #2583: The changes in this PR involve version updates in Cargo.toml, which may relate to the version normalization logic modified in the main PR, as both involve handling versioning in the Dojo 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 55.14%. Comparing base (f4199ae) to head (4c553e6).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2598      +/-   ##
==========================================
+ Coverage   55.13%   55.14%   +0.01%     
==========================================
  Files         385      385              
  Lines       47748    47748              
==========================================
+ Hits        26325    26330       +5     
+ Misses      21423    21418       -5     

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