Skip to content

chore: release v1.6.4 #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 22, 2025
Merged

chore: release v1.6.4 #87

merged 1 commit into from
Apr 22, 2025

Conversation

JounQin
Copy link
Member

@JounQin JounQin commented Apr 22, 2025

πŸ€– New release

  • unrs_resolver: 1.6.3 -> 1.6.4

⚠ unrs_resolver breaking changes

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.40.0/src/lints/inherent_method_missing.ron

Failed in:
  FileSystemOs::strip_windows_prefix, previously in file /tmp/.tmpdiaYmq/unrs_resolver/src/file_system.rs:200
Changelog


This PR was generated with release-plz.


Important

Bump unrs_resolver version to 1.6.4 with a bug fix for DOS device path handling.

  • Version Update:
    • Bump unrs_resolver version from 1.6.3 to 1.6.4 in Cargo.toml, Cargo.lock, and npm/package.json.
  • Bug Fix:
    • Fix handling of DOS device paths in strip_windows_prefix as noted in CHANGELOG.md.

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


Summary by CodeRabbit

  • Documentation
    • Updated the changelog to include a new release entry for version 1.6.4, detailing a bug fix for handling DOS device paths.
  • Chores
    • Bumped the package version to 1.6.4 in both Cargo and npm package files.

@JounQin JounQin force-pushed the release-plz-2025-04-22T13-00-54Z branch from 17f1a7f to 707e15f Compare April 22, 2025 13:01
Copy link

coderabbitai bot commented Apr 22, 2025

Walkthrough

This update finalizes the release of version 1.6.4 for the unrs_resolver project. The changelog is updated with a new release entry dated 2025-04-22 that includes a bug fix for proper handling of DOS device paths in the strip_windows_prefix function. The version numbers in both Cargo.toml and npm/package.json are incremented from 1.6.3 to 1.6.4. No changes were made to exported or public entities.

Changes

Files / Paths Summary of Changes
CHANGELOG.md Added a 1.6.4 release entry for 2025-04-22 including a DOS device path handling fix in strip_windows_prefix.
Cargo.toml Updated the package version from 1.6.3 to 1.6.4.
npm/package.json Updated the package version from 1.6.3 to 1.6.4.

Possibly related PRs

Poem

A hop and a skip, the version climbs,
From 1.6.3 to 1.6.4 in good times!
DOS paths fixed with care and grace,
Bugs now gone without a trace.
This bunny cheers with joyful flair,
New release hops through the air! πŸ‡βœ¨


πŸ“œ 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 707e15f and c494a34.

β›” 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 (1 hunks)
βœ… Files skipped from review due to trivial changes (2)
  • npm/package.json
  • Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Benchmark

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

codecov bot commented Apr 22, 2025

Codecov Report

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

Project coverage is 93.67%. Comparing base (ed82ebd) to head (c494a34).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #87   +/-   ##
=======================================
  Coverage   93.67%   93.67%           
=======================================
  Files          13       13           
  Lines        2844     2844           
=======================================
  Hits         2664     2664           
  Misses        180      180           

β˜” 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

codspeed-hq bot commented Apr 22, 2025

CodSpeed Performance Report

Merging #87 will not alter performance

Comparing release-plz-2025-04-22T13-00-54Z (c494a34) with main (ed82ebd)

Summary

βœ… 3 untouched benchmarks

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: 1

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between ed82ebd and 707e15f.

β›” 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 (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Benchmark
πŸ”‡ Additional comments (4)
Cargo.toml (1)

7-7: Version bump to 2.0.0 is correct.
Major version increment aligns with the semver policy for breaking changes.

npm/package.json (1)

3-3: Version updated to 2.0.0.
Matches the Cargo.toml bumpβ€”good consistency across package metadata.

CHANGELOG.md (2)

11-11: Bug Fixes section is formatted correctly.
The heading follows the Keep a Changelog guidelines and captures the DOS device path fix.


13-13: Verify PR link and description.
Ensure the linked PR #455 correctly points to the unrs/unrs-resolver repository and describes the DOS device path fix.

@JounQin JounQin force-pushed the release-plz-2025-04-22T13-00-54Z branch from 707e15f to c494a34 Compare April 22, 2025 13:08
@JounQin JounQin changed the title chore: release v2.0.0 chore: release v1.6.4 Apr 22, 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 c494a34 in 36 seconds. Click for details.
  • Reviewed 51 lines of code in 4 files
  • Skipped 0 files when reviewing.
  • Skipped posting 6 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. npm/package.json:2
  • Draft comment:
    The version bump to 1.6.4 is consistent with Cargo.toml. The napi configuration and other metadata appear correctly set.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
2. Cargo.toml:12
  • Draft comment:
    Consider removing the leading slashes in the include paths. They should be relative (e.g. "src" instead of "/src") so that Cargo properly identifies the intended files.
  • 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. npm/package.json:3
  • Draft comment:
    Version bump to 1.6.4 is consistent across files.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50% None
4. CHANGELOG.md:64
  • Draft comment:
    Typo detected: 'pacakge.json' should be corrected to 'package.json' for clarity.
  • 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. CHANGELOG.md:443
  • Draft comment:
    Typographical issue: The list entry "* (napi) release wasi build" appears to have a misplaced asterisk and parenthesis. Consider changing it to "- (napi) release wasi build" to maintain consistent 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.
6. npm/package.json:43
  • Draft comment:
    Typographical error: The target 'wasm32-wasip1-threads' may be a typo. If it's meant to be 'wasm32-wasi-threads', please correct it.
  • 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_cz3QHyR0nLLmO6VU

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

@JounQin JounQin merged commit de4bbe4 into main Apr 22, 2025
21 checks passed
@JounQin JounQin deleted the release-plz-2025-04-22T13-00-54Z branch April 22, 2025 13:13
Copy link

@coderabbitai coderabbitai bot mentioned this pull request Apr 23, 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.

1 participant