bump toolchain in semver check

[tomtau]

Summary by CodeRabbit

• Chores
  • Updated the nightly version tag used in the documentation generation process to maintain consistency with current tooling standards.

[coderabbitai]

Walkthrough

The semvercheck.sh script has been updated to change the nightly version tag used in the cargo rustdoc command. The previous tag +nightly-2023-12-31 has been replaced with +nightly-2025-02-20 in both the sections handling current crates and baseline crates. The script’s overall functionality of generating documentation and moving JSON files remains unchanged.

Changes

File(s)	Change Summary
semvercheck.sh	Updated the nightly version tag in the cargo rustdoc command from +nightly-2023-12-31 to +nightly-2025-02-20 in both current and baseline crate sections.

Poem

In my burrow of code I hop with delight,
Replacing old tags with new, getting it right.
The docs are spun with a nightly charm,
Two tweaks in the script, free from harm.
A rabbit’s leap in code—a joyous byte! 🐇

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 803eb68 and ec15551.

📒 Files selected for processing (1)

• semvercheck.sh (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• semvercheck.sh

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

• GitHub Check: Test Coverage
• GitHub Check: cargo hack check --feature-powerset
• GitHub Check: Minimal Versions Testing
• GitHub Check: check for semver compatibility
• GitHub Check: check for no_std compatibility
• GitHub Check: Documentation check
• GitHub Check: Unit, Style, and Lint Testing
• GitHub Check: Fuzzing

---

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