Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Jun 5, 2025

πŸ€– New release

  • unrs_resolver: 1.7.10 -> 1.7.11 (βœ“ API compatible changes)
Changelog

1.7.11 - 2025-06-05

Bug Fixes

  • remove invalid file cache due to extension alias (#136)


This PR was generated with release-plz.


Important

Bump unrs_resolver to v1.7.11 with a bug fix for invalid file cache due to extension alias.

  • Version Update:
    • Bump unrs_resolver version from 1.7.10 to 1.7.11 in Cargo.toml and Cargo.lock.
  • Bug Fix:
    • Remove invalid file cache due to extension alias as noted in CHANGELOG.md.
  • Changelog:
    • Add entry for version 1.7.11 in CHANGELOG.md detailing the bug fix.

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

Summary by CodeRabbit

  • Chores

    • Updated version numbers to 1.7.11 across relevant files.
    • Added a changelog entry for version 1.7.11 documenting a bug fix.
  • Bug Fixes

    • Documented the removal of invalid file cache caused by extension alias issues.

@JounQin JounQin force-pushed the release-plz-2025-06-05T19-01-06Z branch from b7e4108 to acc9212 Compare June 5, 2025 19:01
@coderabbitai
Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

The changes update version numbers to 1.7.11 in the changelog, Cargo.toml, and npm package.json files. The changelog documents a bug fix related to file cache handling. No modifications were made to code, dependencies, or exported entities; only metadata and documentation were updated.

Changes

Files Change Summary
CHANGELOG.md Added entry for version 1.7.11 with a bug fix and PR link.
Cargo.toml Updated package version from 1.7.10 to 1.7.11.
npm/package.json Incremented version to 1.7.11 and updated postinstall script version.

Suggested labels

release

Poem

A hop and a skip, a version anew,
1.7.11, now shining through!
Bugs in the cache have hopped away,
The changelog sings, β€œIt’s a brighter day!”
With numbers aligned, our work is doneβ€”
Release the carrots, let’s have some fun! πŸ₯•


πŸ“œ 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 1bfa253 and acc9212.

β›” 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: Codacy Static Code Analysis
πŸ”‡ Additional comments (4)
Cargo.toml (1)

7-7: Bump crate version to 1.7.11
This version update aligns with the new release documented in CHANGELOG.md.

CHANGELOG.md (1)

10-15: Add changelog entry for v1.7.11
The new entry follows Keep a Changelog format with the correct compare link and PR reference for the bug fix.

npm/package.json (2)

3-3: Bump npm package version to 1.7.11
The version bump is consistent with Cargo.toml and the changelog.


19-19: Update postinstall script to use version 1.7.11
The napi-postinstall argument has been updated to match the new package version.


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

sonarqubecloud bot commented Jun 5, 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 everything up to b7e4108 in 1 minute and 15 seconds. Click for details.
  • Reviewed 43 lines of code in 3 files
  • Skipped 0 files when reviewing.
  • Skipped posting 4 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.7.11 confirmed.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
2. Cargo.toml:12
  • Draft comment:
    Consider removing leading '/' in include paths; use relative paths (e.g., 'src' not '/src').
  • 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.
3. Cargo.toml:27
  • Draft comment:
    Custom clippy lint settings look comprehensive; ensure accompanying docs for maintainability.
  • Reason this comment was not posted:
    Confidence changes required: 30% <= threshold 50% None
4. Cargo.toml:92
  • Draft comment:
    Feature definitions (like 'fs_cache') are clear; verify that 'dep:serde' syntax activates optional deps as intended.
  • Reason this comment was not posted:
    Confidence changes required: 30% <= threshold 50% None

Workflow ID: wflow_HfrElkzOLtv0rSa9

You can customize Ellipsis by changing your verbosity settings, reacting with πŸ‘ or πŸ‘Ž, replying to comments, or adding code review rules.

@JounQin JounQin merged commit 395df2a into main Jun 5, 2025
9 checks passed
@JounQin JounQin deleted the release-plz-2025-06-05T19-01-06Z branch June 5, 2025 19:04
@codecov
Copy link

codecov bot commented Jun 5, 2025

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 93.39%. Comparing base (1bfa253) to head (acc9212).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #137   +/-   ##
=======================================
  Coverage   93.39%   93.39%           
=======================================
  Files          13       13           
  Lines        2890     2890           
=======================================
  Hits         2699     2699           
  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 5, 2025

CodSpeed Performance Report

Merging #137 will not alter performance

Comparing release-plz-2025-06-05T19-01-06Z (acc9212) with main (1bfa253)

Summary

βœ… 3 untouched benchmarks

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