Skip to content

Conversation

@JounQin
Copy link
Member

@JounQin JounQin commented Apr 21, 2025

πŸ€– New release

  • unrs_resolver: 1.6.1 -> 1.6.2 (βœ“ API compatible changes)
Changelog

1.6.2 - 2025-04-21

Bug Fixes

  • resolve parent base url correctly by normalizing as absolute path (#72)


This PR was generated with release-plz.


Important

Bump unrs_resolver to v1.6.2 with a bug fix for parent base URL resolution.

  • Version Update:
    • Bump unrs_resolver version from 1.6.1 to 1.6.2 in Cargo.toml and Cargo.lock.
  • Bug Fix:
    • Fix parent base URL resolution by normalizing as absolute path (see CHANGELOG.md).

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

Summary by CodeRabbit

  • Chores
    • Updated version number to 1.6.2 in preparation for a new release.
    • Added a changelog entry for version 1.6.2, detailing a bug fix related to base URL resolution.

@JounQin JounQin force-pushed the release-plz-2025-04-21T06-21-06Z branch from bddaae5 to 04a494d Compare April 21, 2025 06:21
@coderabbitai
Copy link

coderabbitai bot commented Apr 21, 2025

Walkthrough

This update introduces a new release entry for version 1.6.2 in the changelog, documenting a bug fix related to the normalization of the parent base URL as an absolute path. The version numbers in both the Cargo.toml and npm/package.json files are incremented from 1.6.1 to 1.6.2 to reflect the new release. No other code, configuration, or public API changes are present in this update.

Changes

File(s) Change Summary
CHANGELOG.md Added a new release entry for version 1.6.2 (2025-04-21), documenting a bug fix and referencing PR #72.
Cargo.toml Updated the package version from 1.6.1 to 1.6.2.
npm/package.json Updated the package version from 1.6.1 to 1.6.2.

Possibly related PRs

Poem

A hop and a skip, version bumps anew,
The changelog’s refreshed with a fix in view.
From 1.6.1 to 1.6.2 we stride,
Absolute paths now normalized with pride.
πŸ‡βœ¨
Release notes written, the work is throughβ€”
Another small leap for the resolver crew!


πŸ“œ 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 c299339 and 04a494d.

β›” 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 (2)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Benchmark
πŸ”‡ Additional comments (3)
npm/package.json (1)

3-3: Bump npm package version
The "version" field has been correctly updated from "1.6.1" to "1.6.2" to reflect the new release.

Cargo.toml (1)

7-7: Bump Cargo package version
The version in the [package] section is now "1.6.2", aligning the Rust crate with the new release.

CHANGELOG.md (1)

9-14: Add changelog entry for v1.6.2
The new release entry correctly documents the bug fix (β€œnormalize parent base URL as absolute path”) and references pull requestΒ #72. The formatting adheres to the existing changelog conventions.


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.

@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 bddaae5 in 52 seconds. Click for details.
  • Reviewed 43 lines of code in 3 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. Cargo.toml:12
  • Draft comment:
    Consider using relative paths for the include field (e.g. "src" instead of "/src").
  • Reason this comment was not posted:
    Confidence changes required: 50% <= threshold 50% None
2. Cargo.toml:12
  • Draft comment:
    Use relative paths (e.g. 'src', 'examples', 'benches') in the include fieldβ€”leading '/' may not match as intended.
  • 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:1
  • Draft comment:
    The workspace members list only includes 'napi'. If the current crate should participate as a workspace member, consider adding '.' or clarifying the intended structure.
  • 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.
4. Cargo.toml:10
  • Draft comment:
    Edition is set to '2024'. Ensure that this is intentional and that all users have a compatible toolchain.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment is asking the PR author to ensure that all users have a compatible toolchain, which violates the rule against asking for confirmation or ensuring behavior. However, it does point out a specific change ('Edition is set to '2024'') and asks if this is intentional, which is allowed. The part about ensuring compatibility should be removed.
5. CHANGELOG.md:48
  • Draft comment:
    Typo: 'pacakge.json' should be '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.
6. CHANGELOG.md:427
  • Draft comment:
    Typo: In the line '* (napi) release wasi build', the closing asterisk is missing. It should be '* (napi) release wasi build'.
  • 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_IHNtggAViCYgmjah

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

Codecov Report

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

Project coverage is 93.22%. Comparing base (c299339) to head (04a494d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #74   +/-   ##
=======================================
  Coverage   93.22%   93.22%           
=======================================
  Files          13       13           
  Lines        2850     2850           
=======================================
  Hits         2657     2657           
  Misses        193      193           

β˜” 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 21, 2025

CodSpeed Performance Report

Merging #74 will not alter performance

Comparing release-plz-2025-04-21T06-21-06Z (04a494d) with main (c299339)

Summary

βœ… 3 untouched benchmarks

@JounQin JounQin merged commit 8009e6a into main Apr 21, 2025
22 checks passed
@JounQin JounQin deleted the release-plz-2025-04-21T06-21-06Z branch April 21, 2025 06:23
@coderabbitai coderabbitai bot mentioned this pull request Apr 21, 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