refactor(rust/nanoid): use rand crate instead of getrandom

[arunanshub]

Summary by CodeRabbit

• New Features

  • Streamlined command for running benchmarks in the README.

• Bug Fixes

  • Updated random byte generation method to enhance reliability.

• Chores

  • Removed unnecessary dependency on getrandom from the project configuration.
  • Updated various action versions in workflow configurations to improve build processes.

[coderabbitai]

Walkthrough

The pull request includes updates to the CI workflow configuration, specifically in .github/workflows/ci.yml, where several action versions have been upgraded and job conditions modified. The Cargo.toml file has had the getrandom dependency removed. Additionally, the README.md file has been adjusted to streamline the benchmark command by omitting the file extension. Lastly, the rust/nanoid.rs file has modified the random byte generation method to utilize the rand crate instead of the removed getrandom crate.

Changes

File Path	Change Summary
.github/workflows/ci.yml	- Updated codecov-action from v4.6.0 to v5.0.4. - Updated cibuildwheel to v2.21.3. - Simplified Install uv step. - Added condition for publishing to PyPI based on tag. - Updated permissions for publish job.
Cargo.toml	- Removed dependency on getrandom.
README.md	- Updated benchmark command by removing .svg extension from output path.
rust/nanoid.rs	- Changed get_random_bytes to use rand crate for generating random bytes, retaining error handling.

Possibly related PRs

• ci(workflows): separate build from test #7: The changes in .github/workflows/ci.yml regarding the installation of dependencies and caching mechanisms are related to the updates made in the main PR, which also modifies the CI workflow.
• build(pynanoid): configure CI to publish to pypi on tag publish #11: The modifications to the publish job in .github/workflows/ci.yml to conditionally publish to PyPI are relevant as they align with the changes made in the main PR regarding job conditions and permissions.
• ci(workflow): use codecov to measure coverage #45: The updates to the Upload Coverage Report to Codecov step in the main PR are directly related to the changes made in this PR, which also focuses on enhancing coverage reporting using Codecov.

🐇 In the code we hop and play,
With actions updated, come what may.
Dependencies trimmed, the path is clear,
For benchmarks bright, we hold so dear.
Random bytes now dance with glee,
In the world of code, we're wild and free! 🌟

---

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

🧹 Outside diff range and nitpick comments (1)

rust/nanoid.rs (1)

6-8: Excellent refactor to use rand::thread_rng()!

The change to use thread_rng() is a good improvement because:

• It maintains cryptographic security
• Uses a cached thread-local RNG instance which can improve performance
• Provides more idiomatic Rust code through the builder pattern
• Properly preserves the original error handling semantics

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2263077 and 07b0173.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• assets/benchmark.svg is excluded by !**/*.svg

📒 Files selected for processing (4)

• .github/workflows/ci.yml (1 hunks)
• Cargo.toml (0 hunks)
• README.md (1 hunks)
• rust/nanoid.rs (1 hunks)

💤 Files with no reviewable changes (1)

• Cargo.toml

✅ Files skipped from review due to trivial changes (1)

• README.md

🔇 Additional comments (1)

.github/workflows/ci.yml (1)

114-114: Verify compatibility with Codecov Action v5.

The upgrade from v4.6.0 to v5.0.4 is a major version bump. While the configuration looks correct, please verify that there are no breaking changes in v5 that could affect the coverage reporting workflow.