fix(CI): use nightly for checking

[samueltardieu]

In order to test with not yet released Rust versions, the check step, which is run first, needs to use the most recent compiler.

Summary by CodeRabbit

• Chores
  • Updated our internal build and testing processes to utilize a more advanced version of our core toolset. This update enhances our automated workflows and ensures our quality assurance practices remain aligned with the latest improvements. There are no visible changes to the application's public features.

[coderabbitai]

Walkthrough

This pull request updates the CI workflow configuration by changing the Rust toolchain commands. The .github/workflows/tests.yml file now installs and sets the default Rust toolchain to nightly instead of stable. No adjustments were made to any public or exported entities.

Changes

File	Change Summary
.github/workflows/tests.yml	Replaced rustup install --profile minimal stable with rustup install --profile minimal nightly and updated rustup default stable to rustup default nightly.

Poem

Hoppin' through the code with glee,
I’m a rabbit updating CI, you see.
Stable paths turned to nightly light,
Commands now dance in the moonlit night.
With every hop, our code feels bright!

---

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

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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/tests.yml (2)

15-16: Update Check Job to Use Nightly Toolchain
The commands on lines 15–16 correctly install and set the default Rust toolchain to nightly in the "check" job. This change aligns with the PR objective by ensuring that the CI process tests against the most recent compiler version, capturing potential issues with unreleased Rust features.

Consider adding an inline comment explaining this intentional switch for future maintainers.

---

60-61: Consistent Nightly Setup in Test-Release Job
The updates on lines 60–61 in the "test-release" job mirror the changes made in the "check" job by switching to the nightly toolchain. This consistency helps in validating release builds with the latest Rust features.

If any test failures or compatibility issues emerge due to nightly-specific behavior, please ensure to review and update affected tests accordingly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ce4b565 and b4d79eb.

📒 Files selected for processing (1)

• .github/workflows/tests.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: benchmarks