Skip to content

ci: add rust-version MSRV policy#52

Open
KooshaPari wants to merge 1 commit into
mainfrom
fix/add-rust-version
Open

ci: add rust-version MSRV policy#52
KooshaPari wants to merge 1 commit into
mainfrom
fix/add-rust-version

Conversation

@KooshaPari
Copy link
Copy Markdown
Owner

@KooshaPari KooshaPari commented May 7, 2026

User description

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


Note

Low Risk
Adds an explicit Rust MSRV to workspace metadata; no runtime or logic changes, with only potential impact being build failures on older toolchains.

Overview
Sets an explicit workspace-level minimum supported Rust version by adding rust-version = "1.75" under [workspace.package] in Cargo.toml to enforce an MSRV policy during builds.

Reviewed by Cursor Bugbot for commit 7128ea1. Bugbot is set up for automated code reviews on this repo. Configure here.


CodeAnt-AI Description

Set the minimum supported Rust version to 1.75

What Changed

  • The workspace now declares Rust 1.75 as the minimum version it supports
  • Builds on older Rust toolchains will now fail earlier instead of producing unclear compatibility issues

Impact

✅ Clearer build requirements
✅ Fewer accidental builds on unsupported Rust versions
✅ Earlier failure on outdated toolchains

🔄 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.

Copilot AI review requested due to automatic review settings May 7, 2026 22:26
@gemini-code-assist
Copy link
Copy Markdown

Warning

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

@codeant-ai
Copy link
Copy Markdown

codeant-ai Bot commented May 7, 2026

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
Copy link
Copy Markdown

coderabbitai Bot commented May 7, 2026

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 30 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: 2481345f-d96f-4682-8391-7dd0011be38b

📥 Commits

Reviewing files that changed from the base of the PR and between 76e962f and 7128ea1.

📒 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

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

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label May 7, 2026
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

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 7128ea1. Configure here.

Comment thread Cargo.toml
resolver = "3"

[workspace.package]
rust-version = "1.75"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MSRV 1.75 incompatible with edition 2024 and resolver 3

High Severity

The rust-version = "1.75" is incompatible with resolver = "3" and the edition = "2024" used by all workspace crates. Edition 2024 was stabilized in Rust 1.85, so the MSRV needs to be at least "1.85". As-is, this policy is misleading and will cause CI MSRV checks to fail or give a false promise of compatibility with Rust 1.75.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 7128ea1. Configure here.

Comment thread Cargo.toml
resolver = "3"

[workspace.package]
rust-version = "1.75"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 Architect Review — HIGH

The declared MSRV rust-version = "1.75" is incompatible with the workspace's edition = "2024" crates (and resolver = "3"), so the project cannot actually build on Rust 1.75 despite advertising that as the minimum supported version.

Suggestion: Raise rust-version in [workspace.package] to the true minimum required by the current editions/resolver (i.e., the first stable Rust release that supports edition = "2024" and resolver 3), and keep this value as the single source of truth for MSRV across tooling and documentation.

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:** 16:16
**Comment:**
	*HIGH: The declared MSRV `rust-version = "1.75"` is incompatible with the workspace's `edition = "2024"` crates (and `resolver = "3"`), so the project cannot actually build on Rust 1.75 despite advertising that as the minimum supported version.

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
Copy link
Copy Markdown

codeant-ai Bot commented May 7, 2026

CodeAnt AI finished reviewing your PR.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants