chore: release v1.3.3

[JounQin]

🤖 New release

• unrs_resolver: 1.3.2 -> 1.3.3 (✓ API compatible changes)

Changelog

1.3.3 - 2025-03-29

Testing

• add nested package json case (#40)

---

This PR was generated with release-plz.

Summary by CodeRabbit

• Documentation

  • Updated release notes for the upcoming release (v1.3.3) with a new section detailing testing improvements and handling of nested package cases.

• Chores

  • Synchronized the package version upgrade to 1.3.3 across project configurations for consistent versioning.

[coderabbitai]

Walkthrough

The changes update the project’s version from 1.3.2 to 1.3.3. A new section for version 1.3.3 is added to the CHANGELOG with a "Testing" header and an entry for a nested package JSON case (referencing pull request #40). The version update is also reflected in both the Cargo.toml and npm/package.json files.

Changes

File(s)	Summary of Changes
CHANGELOG.md	Added a new section for version 1.3.3 (dated 2025-03-29) under "Unreleased", including a "Testing" subsection with an entry for a nested package JSON case (#40).
Cargo.toml, npm/.../package.json	Updated package version from 1.3.2 to 1.3.3.

Poem

I'm a rabbit with a cheerful beat,
Hopping through changes, oh so neat!
Version bump, a brand new day,
Changelog tales on a sunny display,
With code carrots lined in a row,
Celebrating upgrades as I go!
🥕🐰

---

📜 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 aa95b44 and fdc9bea.

⛔ 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 as they are similar to previous changes (3)

• npm/package.json
• Cargo.toml
• CHANGELOG.md

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

9-14: Changelog Entry Review:
The new changelog section for version 1.3.3 clearly documents the release date and includes a "Testing" header detailing the nested package JSON case (referencing PR #40). Please verify that the HTML comment (<!-- 6 -->) included in the "Testing" header is intentional (for tooling or documentation purposes) or consider removing it if not needed.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c0c056a and b4eaa3c.

⛔ 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)

🔇 Additional comments (2)

npm/package.json (1)

3-3: Version Update Verified:
The version field has been updated to "1.3.3", which correctly reflects the new release. This change is consistent with the updates in other project files.

Cargo.toml (1)

7-7: Version Bump Confirmed in Cargo.toml:
The package version has been updated to "1.3.3", aligning with the npm/package.json change. This ensures that both Rust and Node environments are on the same release version.

[codspeed-hq]

CodSpeed Performance Report

Merging #41 will not alter performance

_{Comparing release-plz-2025-03-29T04-17-39Z (f5514a1) with main (96e08b4)}

Summary

✅ 3 untouched benchmarks