chore!: no longer require x86-64-v3

[kwaa]

Summary by CodeRabbit

• New Features

  • Introduced a streamlined [build] section in the configuration for improved project requirements.

• Documentation

  • Updated installation guides to clarify the target architecture (x86-64-v3) for optimal performance.
  • Added instructions for users with older processors regarding local builds and configuration adjustments for binary and Docker installations.
  • Removed outdated notes from the Nix installation documentation.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve modifications to the .cargo/config.toml file, where several commented-out target configurations have been removed and replaced with a new [build] section that specifies rustflags for enabling unstable features related to UUID and Tokio. Additionally, documentation updates have been made across various installation guides (binary, Docker, and Nix) to clarify the target architecture used by Hatsu and instructions for users with older processors.

Changes

File	Change Summary
.cargo/config.toml	Removed commented-out target configurations; added [build] section with rustflags for UUID and Tokio.
docs/src/admins/install-binary.md	Updated to note that Hatsu uses x86-64-v3 target architecture; advised older processors to build locally.
docs/src/admins/install-docker.md	Similar updates as above regarding x86-64-v3 architecture and local build instructions for older processors.
docs/src/admins/install-nix.md	Removed note about x86-64-v3 architecture and local build instructions for older processors.

Possibly related PRs

• refactor!: upgrade to axum 0.7 #62: The changes in the main PR regarding the .cargo/config.toml file and the addition of rustflags for unstable features may relate to the overall configuration and dependency management improvements associated with the upgrade to Axum 0.7 in PR refactor!: upgrade to axum 0.7 #62, which also involves updates to the project's dependencies and build configurations.

Suggested labels

enhancement

Poem

🐇 In the land of code where rabbits hop,
Configs are tidy, no more to stop.
With flags for UUID, and Tokio in sight,
Hatsu runs faster, oh what a delight!
Build it with care, for all to see,
A smoother install, for you and me! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 37570d5 and e680e8e.

📒 Files selected for processing (4)

• .cargo/config.toml (1 hunks)
• docs/src/admins/install-binary.md (0 hunks)
• docs/src/admins/install-docker.md (0 hunks)
• docs/src/admins/install-nix.md (0 hunks)

💤 Files with no reviewable changes (3)

• docs/src/admins/install-binary.md
• docs/src/admins/install-docker.md
• docs/src/admins/install-nix.md

🧰 Additional context used

🔇 Additional comments (1)

.cargo/config.toml (1)

Line range hint 4-14: Approval with considerations for unstable features

The changes look good overall. The removal of commented-out target configurations simplifies the file, and the new [build] section with rustflags is well-documented. However, it's important to note that enabling unstable features for UUID and Tokio may have implications:

1. These features may change in future versions, potentially causing breaking changes.
2. It might limit the ability to use stable Rust releases if these features are required.

To ensure these changes align with the PR objectives and project stability requirements, please run the following verification:

This script will help verify that:

1. The project still compiles with the new flags.
2. The unstable features are actually used in the codebase.
3. The CI is using an appropriate Rust version that supports these features.

Please review the results to ensure they align with the project's requirements.

---

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.

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.

[kwaa]

Related: #26