Skip to content

chore: release v1.6.1#70

Merged
JounQin merged 1 commit intomainfrom
chore/release
Apr 20, 2025
Merged

chore: release v1.6.1#70
JounQin merged 1 commit intomainfrom
chore/release

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 20, 2025

Important

Release v1.6.1 with a bug fix disabling mimalloc on Linux aarch64.

  • Version Update:
    • Bump version to 1.6.1 in Cargo.toml, Cargo.lock, and npm/package.json.
  • Bug Fix:
    • Disable mimalloc on Linux with aarch64 as noted in CHANGELOG.md.

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

Summary by CodeRabbit

  • Documentation

    • Updated the changelog to include details for version 1.6.1, including a bug fix and minor wording improvement.
  • Chores

    • Bumped the package version to 1.6.1 in relevant files.

@JounQin JounQin requested a review from Copilot April 20, 2025 07:51
@coderabbitai
Copy link

coderabbitai bot commented Apr 20, 2025

Walkthrough

This update increments the version of the unrs_resolver package from 1.6.0 to 1.6.1 across Cargo.toml and npm's package.json. The changelog documents a bug fix that disables the mimalloc allocator for Linux on the aarch64 architecture and includes a minor wording adjustment in the 1.6.0 bug fixes section. No changes were made to the codebase or exported/public entities beyond versioning and changelog updates.

Changes

File(s) Change Summary
CHANGELOG.md Added 1.6.1 entry with a bug fix disabling mimalloc on Linux aarch64; minor wording change in 1.6.0.
Cargo.toml Updated package version from 1.6.0 to 1.6.1.
npm/package.json Updated package version from 1.6.0 to 1.6.1.

Possibly related PRs

Poem

A hop, a skip, a version jump,
From 1.6.0 to .1 we bump!
Mimalloc rests on aarch64,
Bugs are fixed, and nothing more.
With every patch, we leap ahead—
The changelog’s lines by rabbits read! 🐇✨


📜 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 12dca0c and 056933e.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (2 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Benchmark
🔇 Additional comments (4)
Cargo.toml (1)

7-7: Patch version bump in Cargo manifest
Updated version from "1.6.0" to "1.6.1" to reflect the new patch release.

npm/package.json (1)

3-3: Patch version bump in npm manifest
Updated "version" from "1.6.0" to "1.6.1" to keep npm and Cargo releases in sync.

CHANGELOG.md (2)

9-14: Add changelog entry for v1.6.1
Documented the patch release (2025-04-20) with the bug fix disabling mimalloc on Linux aarch64. Entry follows the Keep a Changelog format.


24-24: Refine changelog wording for v1.6.0
Removed the fix: prefix from the previous bug fix entry to align with the project's changelog style.


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

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 updates the project version from v1.6.0 to v1.6.1 and adjusts the CHANGELOG accordingly to reflect new bug fixes.

  • Bump package version in Cargo.toml
  • Add new bug fixes section in CHANGELOG.md with updated changelog entries

Reviewed Changes

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

File Description
Cargo.toml Version bump to release v1.6.1
CHANGELOG.md Added changelog entries for v1.6.1 with updated bug fix descriptions
Files not reviewed (1)
  • npm/package.json: Language not supported
Comments suppressed due to low confidence (1)

CHANGELOG.md:24

  • [nitpick] The removal of the 'fix:' prefix for the npm-postinstall dependency entry creates an inconsistency with the expected naming format in the bug fixes section. Consider reintroducing the prefix or revising the other entries for consistency.
add `napi-postinstall` dep for workaround `npm`'s bug ([#66](https://github.com/unrs/unrs-resolver/pull/66))

@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Apr 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.20%. Comparing base (77d3bf5) to head (056933e).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   93.20%   93.20%           
=======================================
  Files          13       13           
  Lines        2841     2841           
=======================================
  Hits         2648     2648           
  Misses        193      193           

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

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 056933e in 1 minute and 17 seconds. Click for details.
  • Reviewed 64 lines of code in 4 files
  • Skipped 0 files when reviewing.
  • Skipped posting 11 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 updated to 1.6.1; please ensure it is consistently reflected in all package metadata.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to ensure consistency in versioning across package metadata. It falls under the category of asking the author to double-check things, which is against the rules. Therefore, this comment should be removed.
2. Cargo.toml:90
  • Draft comment:
    Check the default features, especially fs_cache and yarn_pnp, to ensure they're intended for all users.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50% None
3. npm/package.json:3
  • Draft comment:
    Version updated to 1.6.1; verify consistency with Cargo.toml and overall release.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify consistency with Cargo.toml and the overall release, which falls under asking the author to double-check things. This violates the rules as it is not a specific code suggestion or request for a test.
4. npm/package.json:47
  • Draft comment:
    Postinstall script uses 'napi-postinstall unrs-resolver check'. Confirm that 'check' parameter is correct for your intended behavior.
  • 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.
5. Cargo.toml:7
  • Draft comment:
    Version bump to 1.6.1 is correctly applied and consistent.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
6. Cargo.lock:1192
  • Draft comment:
    Cargo.lock reflects the updated package version 1.6.1.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
7. npm/package.json:3
  • Draft comment:
    npm package version updated to 1.6.1, ensuring consistency with Rust crate.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
8. CHANGELOG.md:13
  • Draft comment:
    Typo: 'linux' should be capitalized to 'Linux' since it's a proper noun referring to the operating system.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While technically correct that 'Linux' is typically capitalized as a proper noun, this is a changelog entry and the capitalization doesn't affect functionality. The comment is purely stylistic and not critical. The rules state not to make purely informative comments or comments that are obvious/unimportant. This seems to fall into that category. The capitalization of Linux is a widely accepted convention and could be seen as a legitimate documentation issue since this is user-facing text in the changelog. While proper capitalization is good practice, this minor stylistic issue doesn't rise to the level of requiring a comment. The rules specifically say not to make purely informative comments or comments about obvious/unimportant issues. This comment should be removed as it addresses a minor stylistic issue that doesn't materially affect the project or require immediate action.
9. CHANGELOG.md:42
  • Draft comment:
    Typographical error: '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.
10. CHANGELOG.md:421
  • Draft comment:
    Typographical error: The markdown formatting for the NAPI label appears incorrect. It currently reads '(napi' but should likely be '(napi)' to maintain proper emphasis formatting.
  • 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.
11. npm/package.json:43
  • Draft comment:
    Typographical Error: The target 'wasm32-wasip1-threads' may contain a typo ('wasip1'). Please verify if it should be corrected to 'wasm32-wasi-threads'.
  • 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_fk3NtjfNjBSk8G2H

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

@codspeed-hq
Copy link

codspeed-hq bot commented Apr 20, 2025

CodSpeed Performance Report

Merging #70 will not alter performance

Comparing chore/release (056933e) with main (77d3bf5)

Summary

✅ 3 untouched benchmarks

@JounQin JounQin merged commit da3c6dd into main Apr 20, 2025
22 checks passed
@JounQin JounQin deleted the chore/release branch April 20, 2025 07:53
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