Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 24, 2025

Important

Bump version to 1.6.6 and add new target riscv64gc-unknown-linux-musl.

  • Version Update:
    • Bump version from 1.6.5 to 1.6.6 in Cargo.toml, Cargo.lock, and npm/package.json.
  • Features:
    • Add new target riscv64gc-unknown-linux-musl as documented in CHANGELOG.md.

This description was created by Ellipsis for 79e7737. You can customize this summary. It will automatically update as commits are pushed.

Summary by CodeRabbit

  • Documentation

    • Updated the changelog with a new release entry for version 1.6.6, highlighting added support for the target riscv64gc-unknown-linux-musl.
    • Improved formatting and consistency in previous changelog entries.
  • Chores

    • Bumped the package version to 1.6.6 in project configuration files.

@JounQin JounQin requested a review from Copilot April 24, 2025 01:26
Copy link

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.

Pull Request Overview

This PR is a chore that bumps the project version to v1.6.6 and updates the changelog accordingly.

  • Updated Cargo.toml version field from "1.6.5" to "1.6.6".
  • Added a new release section in CHANGELOG.md with release notes and formatting changes.

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File Description
Cargo.toml Version number updated to reflect the new release.
CHANGELOG.md Added a new changelog entry for version 1.6.6 and updated section headings for consistency.
Files not reviewed (1)
  • npm/package.json: Language not supported

@coderabbitai
Copy link

coderabbitai bot commented Apr 24, 2025

Walkthrough

This update introduces a new release entry for version 1.6.6 in the changelog, highlighting the addition of support for the riscv64gc-unknown-linux-musl target. The changelog also receives minor formatting adjustments for consistency, including updated section headings and horizontal rule separators. Additionally, the version numbers are incremented to 1.6.6 in both the Rust Cargo.toml and the npm package.json files. No changes to code, dependencies, or public interfaces are present.

Changes

File(s) Change Summary
CHANGELOG.md Added 1.6.6 release entry for new target support; updated headings for consistency; added separators
Cargo.toml, npm/package.json Bumped version from 1.6.5 to 1.6.6; no other metadata or config changes

Possibly related PRs

Poem

A hop, a skip, a version hop—
1.6.6, we never stop!
RISC-V support now joins the crew,
With changelog lines and numbers new.
A bunny’s joy, a gentle cheer,
For every tidy, bright new year!
🐰✨


📜 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 faa6985 and 79e7737.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (5 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (7)
Cargo.toml (1)

7-7: Version bump applied
The version field has been correctly updated to "1.6.6", matching the intended release.

npm/package.json (1)

3-3: Version bump applied
The npm package version has been correctly updated to "1.6.6", in sync with Cargo.toml and the changelog.

CHANGELOG.md (5)

9-13: Add 1.6.6 release entry
The new section for [1.6.6] is formatted correctly with the comparison link, release date, hidden “Features” comment, and feature bullet.


177-177: Normalize Features heading for 1.3.0
The hidden HTML comment marker <!-- 0 --> has been consistently added to the “Features” heading in the 1.3.0 entry.


189-189: Normalize Features heading for 1.2.0
The hidden HTML comment marker <!-- 0 --> has been consistently added to the “Features” heading in the 1.2.0 entry.


217-217: Insert horizontal rule after 1.0.0
The --- separator has been correctly inserted to visually distinguish the 1.0.0 section.


341-341: Insert horizontal rule after 5.0.0
The --- separator has been correctly inserted to visually distinguish the 5.0.0 section.


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
🪧 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 generate sequence diagram to generate a sequence diagram of the changes in 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.

@sonarqubecloud
Copy link

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to 79e7737 in 58 seconds. Click for details.
  • Reviewed 91 lines of code in 4 files
  • Skipped 0 files when reviewing.
  • Skipped posting 10 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. Cargo.toml:7
  • Draft comment:
    Version bump to 1.6.6 looks good. Ensure all workspace members and dependent crates are compatible.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
2. npm/package.json:3
  • Draft comment:
    Version updated to 1.6.6; verify that the new target architectures (e.g., riscv64gc-unknown-linux-musl) are supported as expected.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
3. Cargo.lock:1175
  • Draft comment:
    unrs_resolver updated to version 1.6.6 in Cargo.lock; ensure this is in sync with Cargo.toml.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
4. Cargo.lock:1175
  • Draft comment:
    Cargo.lock version updated to 1.6.6 – verifies dependency sync with Cargo.toml.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
5. Cargo.toml:7
  • Draft comment:
    Cargo.toml version bump to 1.6.6 is correct and consistent.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
6. npm/package.json:3
  • Draft comment:
    npm package version updated to 1.6.6, matching Cargo.toml.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
7. npm/package.json:48
  • Draft comment:
    New NAPI target 'riscv64gc-unknown-linux-musl' added as expected.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
8. CHANGELOG.md:85
  • Draft comment:
    Typo detected: 'pacakge.json' should be corrected to 'package.json'.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
9. CHANGELOG.md:468
  • Draft comment:
    Typo detected: Likely an error in formatting the napi note. Consider correcting '* (napi)' to properly close the parentheses (e.g., '* (napi)' or similar).
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
10. npm/package.json:44
  • Draft comment:
    Typographical error detected: In the 'napi.targets' array, the target 'wasm32-wasip1-threads' on line 44 seems to have a typo. It might intended to be 'wasm32-wasi-threads'. Please verify and correct if necessary.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_3DCuaZjJT28AnnvR

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@codecov
Copy link

codecov bot commented Apr 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.40%. Comparing base (0461da3) to head (79e7737).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #97   +/-   ##
=======================================
  Coverage   93.40%   93.40%           
=======================================
  Files          13       13           
  Lines        2865     2865           
=======================================
  Hits         2676     2676           
  Misses        189      189           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@codspeed-hq
Copy link

codspeed-hq bot commented Apr 24, 2025

CodSpeed Performance Report

Merging #97 will not alter performance

Comparing chore/release (79e7737) with main (0461da3)

Summary

✅ 3 untouched benchmarks

@JounQin
Copy link
Member Author

JounQin commented Apr 24, 2025

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Apr 24, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@JounQin JounQin merged commit 05b094f into main Apr 24, 2025
23 checks passed
@JounQin JounQin deleted the chore/release branch April 24, 2025 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants