Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented May 28, 2025

🤖 New release

  • unrs_resolver: 1.7.3 -> 1.7.4 (✓ API compatible changes)
Changelog

Bug Fixes

  • prefer file over package dir in node_modules (#116)


This PR was generated with release-plz.


Important

Bump unrs_resolver to version 1.7.4 with a bug fix prioritizing files over package directories in node_modules.

  • Version Update:
    • Bump unrs_resolver version from 1.7.3 to 1.7.4 in Cargo.toml and Cargo.lock.
  • Bug Fix:
    • Prefer file over package directory in node_modules as per CHANGELOG.md entry for version 1.7.4.
  • Changelog:
    • Add entry for version 1.7.4 in CHANGELOG.md detailing the bug fix.

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

Summary by CodeRabbit

  • Bug Fixes

    • Improved module resolution to prefer files over package directories within dependencies.
  • Chores

    • Updated version numbers to 1.7.4 in project files.
    • Added a new release entry to the changelog.

@JounQin JounQin force-pushed the release-plz-2025-05-28T10-08-42Z branch from 4f38645 to 95dd68c Compare May 28, 2025 10:08
@coderabbitai
Copy link

coderabbitai bot commented May 28, 2025

Walkthrough

The changes update the project version to 1.7.4 across Cargo.toml, package.json, and CHANGELOG.md. The changelog records a bug fix for module resolution in node_modules, referencing pull request #116. The postinstall script in package.json is also updated to use the new version number.

Changes

Files Change Summary
CHANGELOG.md Added 1.7.4 release entry with a bug fix for module resolution, referencing PR #116.
Cargo.toml Updated package version from 1.7.3 to 1.7.4.
npm/package.json Updated version from 1.7.3 to 1.7.4; updated postinstall script to use new version number.

Suggested labels

release

Poem

A hop, a skip, to version four,
The changelog tells of bugs no more.
The numbers climb, the scripts align,
In node_modules, all resolve just fine.
With every patch, we leap ahead—
Another carrot for the thread! 🥕


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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 4f38645 in 47 seconds. Click for details.
  • Reviewed 43 lines of code in 3 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 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:12
  • Draft comment:
    The include paths are written with a leading slash. They should be relative (e.g. "src", "examples", "benches") to ensure proper packaging.
  • 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.
2. Cargo.toml:94
  • Draft comment:
    The fs_cache feature lists dependencies with a 'dep:' prefix. Standard Cargo syntax requires using the dependency names directly (e.g. "serde", "serde_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.

Workflow ID: wflow_Mrrp6OeZ6gtOYrDm

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 May 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.42%. Comparing base (ff4799e) to head (95dd68c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   93.42%   93.42%           
=======================================
  Files          13       13           
  Lines        2876     2876           
=======================================
  Hits         2687     2687           
  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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

13-13: Nitpick: Improve changelog bullet wording
Consider refining the phrasing for clarity and grammar:

- - prefer file over package dir in `node_modules` ([#116](https://github.com/unrs/unrs-resolver/pull/116))
+ - prefer a file over a package directory in `node_modules` ([#116](https://github.com/unrs/unrs-resolver/pull/116))
🧰 Tools
🪛 LanguageTool

[grammar] ~13-~13: Consider using “to” with “prefer”.
Context: ... 2025-05-28 ### Bug Fixes - prefer file over package dir in node_modules ([#116](https://g...

(PREFER_OVER_TO)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ff4799e and 95dd68c.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • Cargo.toml (1 hunks)
  • npm/package.json (2 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[grammar] ~13-~13: Consider using “to” with “prefer”.
Context: ... 2025-05-28 ### Bug Fixes - prefer file over package dir in node_modules ([#116](https://g...

(PREFER_OVER_TO)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Benchmark
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (4)
Cargo.toml (1)

7-7: Bump crate version in Cargo.toml
The version has been correctly updated from "1.7.3" to "1.7.4" to reflect the new release.

npm/package.json (2)

3-3: Update package version
The "version" field was updated to "1.7.4" to align with the new release.


19-19: Update postinstall script version
The postinstall script argument now uses the new version "1.7.4".

CHANGELOG.md (1)

9-14: Add changelog entry for v1.7.4
The new release entry is properly formatted with the date and PR link for the bug fix.

🧰 Tools
🪛 LanguageTool

[grammar] ~13-~13: Consider using “to” with “prefer”.
Context: ... 2025-05-28 ### Bug Fixes - prefer file over package dir in node_modules ([#116](https://g...

(PREFER_OVER_TO)

@codspeed-hq
Copy link

codspeed-hq bot commented May 28, 2025

CodSpeed Performance Report

Merging #117 will not alter performance

Comparing release-plz-2025-05-28T10-08-42Z (95dd68c) with main (ff4799e)

Summary

✅ 3 untouched benchmarks

@JounQin JounQin merged commit e1c93e9 into main May 28, 2025
23 checks passed
@JounQin JounQin deleted the release-plz-2025-05-28T10-08-42Z branch May 28, 2025 10:14
@coderabbitai coderabbitai bot mentioned this pull request Jun 5, 2025
@coderabbitai coderabbitai bot mentioned this pull request Jun 20, 2025
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