Skip to content

chore: release v1.7.2#107

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

chore: release v1.7.2#107
JounQin merged 1 commit intomainfrom
chore/release

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 27, 2025

Bug Fixes

  • bump napi-postinstall to fix yarn pnp compatibility issue (#106)

Important

Release v1.7.2 with a bug fix for yarn pnp compatibility and version updates.

  • Bug Fixes:
    • Bump napi-postinstall to fix yarn pnp compatibility issue as noted in CHANGELOG.md.
  • Version Updates:
    • Update version to 1.7.2 in Cargo.toml, Cargo.lock, and npm/package.json.
  • Misc:
    • Move @atlaskit/pragmatic-drag-and-drop from devDependencies to dependencies in fixtures/pnp/package.json.

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

Summary by CodeRabbit

  • Bug Fixes

    • Updated a dependency to resolve a compatibility issue with Yarn Plug'n'Play (PnP).
  • Chores

    • Bumped package version to 1.7.2.
    • Updated changelog to include the latest release information.
    • Adjusted dependency management in package configuration files.

@JounQin JounQin requested a review from Copilot April 27, 2025 04:05
@JounQin JounQin self-assigned this Apr 27, 2025
@coderabbitai
Copy link

coderabbitai bot commented Apr 27, 2025

Walkthrough

This update increments the version number of the package to 1.7.2 across relevant files and updates the changelog to document the release. The changelog entry specifies that the release addresses a compatibility issue with Yarn Plug'n'Play by bumping the napi-postinstall dependency, referencing PR #106. Additionally, the postinstall script in the npm package is updated to use the new version, and a dependency in a fixture package is moved from devDependencies to dependencies. No changes to exported or public entities or core logic are present.

Changes

File(s) Change Summary
CHANGELOG.md Added release entry for version 1.7.2, documenting a bug fix for Yarn PnP compatibility via #106.
Cargo.toml, npm/package.json Updated package version from 1.7.1 to 1.7.2; updated postinstall script in npm/package.json.
fixtures/pnp/package.json Moved "@atlaskit/pragmatic-drag-and-drop" from devDependencies to dependencies; removed devDependencies.

Possibly related PRs

Poem

Hopping ahead, a version anew,
1.7.2 brings a fix in view!
With changelogs neat and scripts aligned,
Dependencies moved, all well-defined.
Now Yarn PnP will play along,
The package hops where it belongs!
🐇✨


📜 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 3a764d9 and 82a9cd3.

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

5-5: Move dependency to dependencies for Yarn PnP compatibility

Moving @atlaskit/pragmatic-drag-and-drop into the dependencies section ensures it’s available at runtime under Plug’n’Play environments.

Cargo.toml (1)

7-7: Bump package version to 1.7.2

Updating version = "1.7.2" aligns this crate with the new release and matches changes in other package manifests.

npm/package.json (2)

3-3: Update npm package version to 1.7.2

The version field was correctly incremented to 1.7.2, matching the Cargo.toml bump and changelog entry.


19-19: Update postinstall script to use new version

The postinstall command now references version 1.7.2, ensuring the correct binary is fetched after install.

CHANGELOG.md (1)

9-14: Add changelog entry for v1.7.2

The new section under “Unreleased” documents the PnP compatibility bug fix (PR #106) and uses the correct compare link and date.


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.

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 pull request prepares the v1.7.2 release by updating the package version and changelog.

  • Updated Cargo.toml to bump package version from 1.7.1 to 1.7.2.
  • Added a changelog entry in CHANGELOG.md for the new release including a note on a bug fix with npm-postinstall.

Reviewed Changes

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

File Description
Cargo.toml Bumped package version to support v1.7.2 release.
CHANGELOG.md Added new release entry with bug fix details.
Files not reviewed (2)
  • fixtures/pnp/package.json: Language not supported
  • npm/package.json: Language not supported

@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 82a9cd3 in 1 minute and 4 seconds. Click for details.
  • Reviewed 84 lines of code in 5 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 updated to 1.7.2; please ensure all related docs and version references (e.g. in Cargo.lock) remain consistent.
  • 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 documentation and version references, which falls under the category of asking the author to double-check things. This violates the rule against asking the author to ensure or verify things.
2. npm/package.json:3
  • Draft comment:
    Version bump to 1.7.2; verify that it matches the native (Rust) version update.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is related to a version bump, which falls under dependency changes. The rules specify not to comment on pure dependency changes or library versions that are not recognized. Therefore, this comment should be removed.
3. npm/package.json:19
  • Draft comment:
    Postinstall script now uses version 1.7.2; ensure this is in sync with the overall version bump.
  • Reason this comment was not posted:
    Comment looked like it was already resolved.
4. fixtures/pnp/package.json:1
  • Draft comment:
    No version bump required here; just ensure consistency with pnp dependencies if needed.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
5. Cargo.toml:7
  • Draft comment:
    Version bumped to 1.7.2; this update looks consistent with the release.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is related to a version bump, which falls under dependency changes. The comment is asking the author to ensure consistency with the release, which is not specific enough and violates the rule against asking the author to ensure things.
6. Cargo.lock:1174
  • Draft comment:
    Lock file updated with unrs_resolver version 1.7.2; ensure the regeneration is correct.
  • 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 that the lock file regeneration is correct, which falls under the rule of not asking the author to double-check things. It also mentions a specific version of a dependency, which is not recognized as a valid comment type according to the rules.
7. fixtures/pnp/package.json:1
  • Draft comment:
    PnP fixture file looks correctly defined with expected dependencies.
  • 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.
8. npm/package.json:3
  • Draft comment:
    npm package.json is updated: version and postinstall command reflect 1.7.2 release.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it only states that the package.json file has been updated to reflect a new version and postinstall command. It does not provide any actionable feedback or suggestions for improvement.
9. CHANGELOG.md:107
  • 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.
10. CHANGELOG.md:450
  • Draft comment:
    Typographical error: 'it self' should be corrected to 'itself'.
  • 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. CHANGELOG.md:490
  • Draft comment:
    Typographical error: The marker *(napi*) appears malformed. Consider correcting it to *(napi)* to ensure proper 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.

Workflow ID: wflow_sNcGrRaCTU99tgYP

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 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.40%. Comparing base (1873179) to head (82a9cd3).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  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 27, 2025

CodSpeed Performance Report

Merging #107 will not alter performance

Comparing chore/release (82a9cd3) with main (1873179)

Summary

✅ 3 untouched benchmarks

@JounQin JounQin merged commit 1e36ffe into main Apr 27, 2025
23 checks passed
@JounQin JounQin deleted the chore/release branch April 27, 2025 04:09
This was referenced May 27, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jun 5, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jun 20, 2025
This was referenced Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants