Update stable toolchain in CI

[magicant]

GitHub Actions images are updated regularly, but sometimes the
preinstalled Rust toolchain is not the latest stable release. This
commit updates the stable toolchain to the latest version in the CI
workflow.

Summary by CodeRabbit

• Chores
  • Updated CI workflow configuration to use stable Rust toolchain across multiple jobs.

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow configuration file to standardize the Rust toolchain setup across multiple CI jobs. By introducing the dtolnay/rust-toolchain@stable action in the check, clippy, extra, and windows jobs, the workflow ensures a consistent Rust environment is used during continuous integration processes.

Changes

File	Change Summary
.github/workflows/ci.yml	Added dtolnay/rust-toolchain@stable action to multiple jobs to standardize Rust toolchain setup

Poem

🐰 A Rust Workflow Tale

Stable toolchain, a rabbit's delight
CI jobs now shine so bright
Actions dancing, workflow clean
Consistency is now our dream
Hopping through code with glee! 🚀

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/ci.yml (2)

64-64: LGTM! Proper toolchain setup for the windows job.

The stable toolchain setup is correctly placed. However, since the project supports multiple Rust versions (as seen in the msrv job), consider adding a comment explaining why the stable toolchain is specifically needed for Windows testing.

+    # Using stable toolchain for Windows testing as it provides the most reliable environment
     - uses: dtolnay/rust-toolchain@stable

---

Line range hint 21-64: Great job on maintaining workflow consistency!

The addition of dtolnay/rust-toolchain@stable is consistently applied across all relevant jobs while preserving backward compatibility through the msrv job. This change effectively addresses the PR's objective of ensuring the latest stable Rust toolchain is used in CI.

Consider adding a comment in the workflow's header documenting this standardization of the Rust toolchain setup for future maintainers.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 909dbe6 and 19f56b7.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (3 hunks)

🔇 Additional comments (3)

.github/workflows/ci.yml (3)

21-21: LGTM! Proper toolchain setup for the check job.

The placement of the stable toolchain setup is correct (after checkout, before cache) and aligns with the PR's objective of ensuring the latest stable Rust version is used.

---

29-29: LGTM! Proper toolchain setup for the clippy job.

The stable toolchain setup is correctly placed and will ensure consistent clippy analysis with the latest stable Rust version.

---

40-40: LGTM! Proper toolchain setup for the extra job.

The stable toolchain setup is correctly placed and will ensure consistent environment for additional tools like cargo-tomlfmt.