chore(deps): update all dependencies #471
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community 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 (
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
commit: |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
size-limit report 📦
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #471 +/- ##
=======================================
Coverage 63.93% 63.93%
=======================================
Files 6 6
Lines 391 391
Branches 50 50
=======================================
Hits 250 250
Misses 141 141 ☔ 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 122ed61 in 1 minute and 6 seconds. Click for details.
- Reviewed
20lines of code in2files - Skipped
1files 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. .nvmrc:1
- Draft comment:
Ensure the updated Node version (22.18.0) is intentional. This version now aligns with the newer dependency requirements, but double-check that all dev and CI environments are prepared for this update. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to ensure that the updated Node version is intentional and to double-check that all environments are prepared for the update. This violates the rule against asking the author to confirm their intention or to double-check things. The comment does not provide a specific code suggestion or ask for a specific test to be written.
2. package.json:109
- Draft comment:
tsdown has been updated to ^0.13.0 which now requires Node ≥20.19. However, the engines field still allows Node versions as low as 16.17.0 or 18.6.0. Consider updating the engines field or documenting the required Node version for development. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is about a devDependency, not a runtime dependency. The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." Additionally, without being able to verify tsdown's actual Node requirements, this is somewhat speculative. The package author likely tested the update before committing it. Maybe there could be real development environment setup issues for contributors if the Node version requirements aren't properly documented. While documentation could be helpful, the rules are clear about not commenting on dependency changes, and this is a devDependency which only affects development setup. Delete this comment as it violates the rule about not commenting on dependency changes and versions.
Workflow ID: wflow_nAVchd7uZCPE5G5P
You can customize 
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
22.17.0->22.18.0^0.12.7->^0.13.0Release Notes
nodejs/node (node)
v22.18.0Compare Source
v22.17.1Compare Source
rolldown/tsdown (tsdown)
v0.13.0Compare Source
🚨 Breaking Changes
🚀 Features
banner&footeroptions - by @gwansikk and @sxzz in https://github.com/rolldown/tsdown/issues/338 (54e21)cjsDtsto input/output options context - by @sxzz (3c4b3)🐞 Bug Fixes
View changes on GitHub
v0.12.9Compare Source
🚀 Features
nodeProtocoloption - by @ryoppippi and @sxzz in https://github.com/rolldown/tsdown/issues/336 (b3f67)View changes on GitHub
v0.12.8Compare Source
🚀 Features
bundleoption - by @sxzz (d6faa)ResolvedOptions- by @sxzz (13d9c)🐞 Bug Fixes
lastIndexfor regex - by @btea in https://github.com/rolldown/tsdown/issues/320 (1abc9)View changes on GitHub
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
Important
Update
nodeandtsdowndependencies to latest versions, including breaking changes fortsdown.nodeversion in.nvmrcfrom22.17.0to22.18.0.tsdownversion inpackage.jsonfrom^0.12.7to^0.13.0.tsdownnow requires Node 20.19+ and reuses generated dts by default.This description was created by
for 122ed61. You can customize this summary. It will automatically update as commits are pushed.