ci: add rust-version MSRV policy

[KooshaPari]

User description

Adds explicit rust-version = "1.75" MSRV policy to Cargo.toml.

---

Note

Low Risk
Low risk: it only pins the minimum supported Rust version for builds, but may break CI/users compiling with older toolchains.

Overview
Adds a [workspace.package] section to Cargo.toml and sets rust-version = "1.75" to enforce a workspace-wide minimum supported Rust version (MSRV) for the project.

^{Reviewed by Cursor Bugbot for commit 58a7283. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Set the project’s minimum supported Rust version to 1.75

What Changed

• The workspace now requires Rust 1.75 or newer to build
• Older Rust toolchains will no longer be accepted for this project

Impact

✅ Fewer build failures on unsupported toolchains
✅ Clearer Rust version requirements for contributors
✅ More consistent CI and local builds

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 46 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fe6a8127-1d17-426b-b06b-bc5cb28b40f8

📥 Commits

Reviewing files that changed from the base of the PR and between 41d417c and 58a7283.

📒 Files selected for processing (1)

• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/add-rust-version

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch fix/add-rust-version

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because on-demand usage is turned off. To enable Bugbot Autofix, turn on on-demand usage and set a spend limit in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 58a7283. Configure here.}

[cursor]

TOML section ordering misplaces workspace keys under wrong table

High Severity

The [workspace.package] header is inserted on line 2, immediately after [workspace] and before members and resolver. In TOML, all key-value pairs after a section header belong to that section until a new header appears. This causes members and resolver to be parsed as keys of [workspace.package] instead of [workspace], which breaks the workspace configuration entirely. The [workspace.package] block needs to appear after the members and resolver keys.

 

^{Reviewed by Cursor Bugbot for commit 58a7283. Configure here.}

[codeant-ai]

🔴 Architect Review — CRITICAL

[workspace.package] is opened before members and resolver, so those keys now belong to workspace.package instead of [workspace], leaving the actual [workspace] table without members or resolver and breaking the workspace definition Cargo expects.

Suggestion: Keep members and resolver directly under [workspace] (e.g., place them immediately after [workspace]), then define [workspace.package] and rust-version = "1.75" after that so workspace members and resolver are correctly scoped.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** Cargo.toml
**Line:** 2:10
**Comment:**
	*CRITICAL: `[workspace.package]` is opened before `members` and `resolver`, so those keys now belong to `workspace.package` instead of `[workspace]`, leaving the actual `[workspace]` table without `members` or `resolver` and breaking the workspace definition Cargo expects.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.