chore: release v1.11.0 #179
Conversation
JounQin
force-pushed
the
release-plz-2025-07-06T12-16-54Z
branch
from
f055f8c to
621acb0
Compare
|
Warning Rate limit exceeded@JounQin has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 36 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #179 +/- ##
=======================================
Coverage 95.10% 95.10%
=======================================
Files 12 12
Lines 2818 2818
=======================================
Hits 2680 2680
Misses 138 138 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to f055f8c in 1 minute and 46 seconds. Click for details.
- Reviewed
64lines of code in3files - Skipped
0files when reviewing. - Skipped posting
2draft 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:
The include paths use leading '/' which makes them look absolute. Consider using relative paths (e.g. 'src', 'examples', 'benches') to avoid potential packaging issues. - 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.
2. CHANGELOG.md:16
- Draft comment:
Typo: Consider using 'lookup' instead of 'look up' in "rework yarn manifest file look up" for better clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% This is a very minor stylistic suggestion about word choice in documentation. Both "look up" and "lookup" are technically correct - "look up" is the verb form and "lookup" is the noun form. The comment isn't pointing out an actual error. Changelogs are meant to document changes, not be perfectly styled documents. The comment could be technically correct if "lookup" is the standard term used throughout the codebase. Consistency in terminology can be important. While consistency is good, this is too minor of an issue to warrant a comment. The meaning is clear either way, and this is just documentation, not code. Delete this comment as it's an extremely minor stylistic suggestion about documentation that doesn't impact functionality or clarity.
Workflow ID: wflow_6i5OBoIF3u9daSEf
You can customize 
CodSpeed Performance ReportMerging #179 will not alter performanceComparing Summary
|
🤖 New release
unrs_resolver: 1.10.1 -> 1.11.0Changelog
This PR was generated with release-plz.
Important
Release v1.11.0 of
unrs_resolverwith new features, refactoring, and version bump.unrs_resolverversion from 1.10.1 to 1.11.0 inCargo.tomlandCargo.lock.yarn_pnplogic toFileSystem.fs_cachefeature flag.This description was created by
for f055f8c. You can customize this summary. It will automatically update as commits are pushed.