Skip to content

chore: release v1.7.12#140

Merged
JounQin merged 1 commit intomainfrom
release-plz-2025-06-09T14-27-51Z
Jun 9, 2025
Merged

chore: release v1.7.12#140
JounQin merged 1 commit intomainfrom
release-plz-2025-06-09T14-27-51Z

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Jun 9, 2025

🤖 New release

  • unrs_resolver: 1.7.11 -> 1.7.12 (✓ API compatible changes)
Changelog

1.7.12 - 2025-06-09

Bug Fixes

  • npm protocol alias with pnp should be supported (#139)


This PR was generated with release-plz.


Important

Bump unrs_resolver to v1.7.12 with a bug fix for npm protocol alias with pnp support.

  • Version Update:
    • Bump unrs_resolver version from 1.7.11 to 1.7.12 in Cargo.toml, Cargo.lock, and npm/package.json.
  • Bug Fix:
    • Support npm protocol alias with pnp as per changelog entry for version 1.7.12.
  • Changelog:
    • Update CHANGELOG.md to include details of the bug fix in version 1.7.12.

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

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue to support npm protocol alias with Plug'n'Play (PnP).
  • Chores

    • Updated package version to 1.7.12 across relevant files.
    • Added a new release entry to the changelog.

@coderabbitai
Copy link

coderabbitai bot commented Jun 9, 2025

Walkthrough

This update increments the version number to 1.7.12 across Cargo.toml and npm's package.json, updates the changelog with a new entry for the release, and adjusts the npm postinstall script to use the new version. The changelog notes a bug fix for npm protocol alias support with Plug'n'Play.

Changes

File(s) Summary of Changes
CHANGELOG.md Added 1.7.12 release entry with bug fix for npm protocol alias with pnp.
Cargo.toml Updated package version from 1.7.11 to 1.7.12.
npm/package.json Updated version to 1.7.12; updated postinstall script to match new version.

Possibly related PRs

  • chore: release v1.6.0 #68: Updates version number and changelog for a previous release, related through versioning and release management.

Suggested labels

release

Poem

The numbers hop, a version new,
1.7.12 now hops in view!
With changelog fresh and scripts aligned,
npm and Cargo, all combined.
A bug was fixed, the alias found—
The rabbit leaps, no bugs around! 🐇✨


📜 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 6f3d3d4 and 3081c35.

⛔ 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)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test (windows-latest)
🔇 Additional comments (4)
CHANGELOG.md (1)

10-15: Changelog entry aligns with version bump and bug fix details.

The new 1.7.12 entry is correctly formatted, dated, and references PR #139 under the “Unreleased” section.

Cargo.toml (2)

7-7: Version bumped to 1.7.12 in Cargo.toml.

This matches the changelog entry and the npm package.json version.


7-7:

Details

✅ Verification successful

Ensure Cargo.lock updated

PR objectives mention bumping Cargo.lock as well. Please verify that Cargo.lock no longer contains references to version 1.7.11.


🏁 Script executed:

#!/usr/bin/env bash
# Verify that Cargo.lock has no lingering references to version 1.7.11
if rg -n 'version = "1\.7\.11"' Cargo.lock; then
  echo "❌ Found old version references in Cargo.lock"
  exit 1
else
  echo "✅ Cargo.lock updated correctly."
fi

Length of output: 114


Cargo.lock updated successfully

No references to version 1.7.11 remain in Cargo.lock—everything’s up to date. 🎉

npm/package.json (1)

3-3: Version and postinstall script updated to 1.7.12

The version field and the postinstall script argument now match the new release version.

Also applies to: 19-19


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.

@JounQin JounQin force-pushed the release-plz-2025-06-09T14-27-51Z branch from bdda96d to 3081c35 Compare June 9, 2025 14:28
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 9, 2025

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 3081c35 in 38 seconds. Click for details.
  • Reviewed 64 lines of code in 4 files
  • Skipped 0 files when reviewing.
  • Skipped posting 5 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. CHANGELOG.md:10
  • Draft comment:
    New version entry for 1.7.12 looks correct and includes the bug fix for npm protocol alias with pnp.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
2. Cargo.lock:1235
  • Draft comment:
    Version for unrs_resolver updated to 1.7.12; ensure Cargo.lock is regenerated and in sync with Cargo.toml.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
3. Cargo.toml:7
  • Draft comment:
    The package version in Cargo.toml is correctly updated to 1.7.12.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
4. npm/package.json:3
  • Draft comment:
    Version bump to 1.7.12 in package.json is consistent.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
5. npm/package.json:19
  • Draft comment:
    The postinstall script now reflects version 1.7.12; ensure this matches the released binary version.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_ScvZK01ui5DDpmj6

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

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 bdda96d in 59 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:10
  • Draft comment:
    Verify that using edition = "2024" is intentional. This edition is not yet stable and may require a future compiler or nightly toolchain.
  • Reason this comment was not posted:
    Comment was on unchanged code.
2. Cargo.toml:12
  • Draft comment:
    The include paths start with a leading '/' which makes them absolute. Consider using relative paths (e.g. 'src', 'examples', 'benches').
  • 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_HGQ0pFkmcMPMmFvx

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 Jun 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.40%. Comparing base (6f3d3d4) to head (3081c35).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #140   +/-   ##
=======================================
  Coverage   93.40%   93.40%           
=======================================
  Files          13       13           
  Lines        2894     2894           
=======================================
  Hits         2703     2703           
  Misses        191      191           

☔ 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 Jun 9, 2025

CodSpeed Performance Report

Merging #140 will not alter performance

Comparing release-plz-2025-06-09T14-27-51Z (3081c35) with main (6f3d3d4)

Summary

✅ 3 untouched benchmarks

@JounQin JounQin merged commit acccae1 into main Jun 9, 2025
23 checks passed
@JounQin JounQin deleted the release-plz-2025-06-09T14-27-51Z branch June 9, 2025 15:42
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.

1 participant