chore(deps): update all dependencies #12
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&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: |
![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 aa33f41 in 40 seconds. Click for details.
- Reviewed
45lines of code in2files - Skipped
1files when reviewing. - Skipped posting
5draft 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. .github/workflows/autofix.yml:34
- Draft comment:
Verify that updating the autofix-ci action commit (now using 635ffb0c9798bd160680f18fd73371e355b85f27) behaves as expected and is safe from a security perspective. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to verify the behavior and security of a change, which is against the rules. It does not provide a specific suggestion or point out a specific issue with the code.
2. package.json:64
- Draft comment:
Ensure the updated '@types/web' (^0.0.243) does not introduce unexpected type changes in DOM interfaces. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to ensure that the updated dependency does not introduce unexpected changes. It is related to dependency changes, which is against the rules for making comments.
3. package.json:67
- Draft comment:
Confirm that '@vitest/coverage-v8' update to 3.2.4 is fully compatible with existing tests and coverage reports. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to confirm compatibility of a dependency update, which is against the rules. It does not provide a specific suggestion or point out a specific issue with the code.
4. package.json:89
- Draft comment:
Major version bump for 'vite' (^7.0.0) may include breaking changes; ensure thorough testing and review of migration guides. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is about a major version bump for a dependency, which is related to dependencies. The rules specify not to comment on pure dependency changes or library versions that are not recognized. This comment is asking for thorough testing and review, which is not allowed.
5. package.json:97
- Draft comment:
Review the change in the 'resolutions' field for 'vite'; switching from 'npm:rolldown-vite@^6.3.17' to '^7.0.0' might affect dependency resolution. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =30%<= threshold50%The comment is about a change in the 'resolutions' field for a dependency. It suggests that the change might affect dependency resolution, which is a valid concern. However, it doesn't ask the author to confirm the intention or provide a specific suggestion. It is more of a cautionary note, which is not allowed by the rules.
Workflow ID: wflow_8mTbiJrjKbJhFVJ3
You can customize 
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
📊 Package size report -0.01%↓
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 69 69
Branches 26 26
=========================================
Hits 69 69 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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. |
JounQin
reviewed
Jun 25, 2025
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed b292eec in 1 minute and 16 seconds. Click for details.
- Reviewed
65lines of code in1files - Skipped
0files when reviewing. - Skipped posting
12draft 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. package.json:54
- Draft comment:
Bump @1stg/common-config to ^14.2.0. Confirm no breaking changes with updated config. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is related to a dependency change, specifically bumping a version of a package. The comment asks to confirm no breaking changes, which is against the rules as it asks the author to ensure something. Therefore, this comment should be removed.
2. package.json:56
- Draft comment:
Upgrade @changesets/cli to ^2.29.5; a minor patch bump which should be safe. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative, discussing a dependency upgrade and its perceived safety. It doesn't provide a specific suggestion or highlight a potential issue with the code.
3. package.json:60
- Draft comment:
Update @shikijs/rehype to ^3.7.0. Check if any breaking changes affect the rehype processing. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is related to a dependency update and asks the author to check for breaking changes, which is against the rules. It doesn't provide a specific suggestion or point out a specific issue with the code.
4. package.json:61
- Draft comment:
Bump @types/node to ^22.15.33. This patch update should enhance type support without issues. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative and discusses a dependency change, which is not allowed according to the rules. It doesn't provide any actionable feedback or suggestions for improvement.
5. package.json:62
- Draft comment:
Upgrade @types/react to ^19.1.8 for improved typings. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative and relates to a dependency change. It doesn't provide a specific suggestion or highlight a potential issue with the code. According to the rules, purely informative comments and comments on dependency changes should be removed.
6. package.json:66
- Draft comment:
Update @vitejs/plugin-react-swc to ^3.10.2. Ensure compatibility with current Vite and React setups. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about updating a dependency version and ensuring compatibility, which falls under the rule of not commenting on dependency changes or asking the author to ensure compatibility. Therefore, this comment should be removed.
7. package.json:70
- Draft comment:
Upgrade eslint to ^9.29.0. A patch update to improve linting performance and fixes. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative, providing details about a dependency update. It doesn't suggest any action or raise any concerns about the change.
8. package.json:78
- Draft comment:
Update prettier in devDependencies to ^3.6.1. Verify that formatting rules remain consistent with the team’s config. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to verify that formatting rules remain consistent, which is against the rules. It is related to dependency changes, which should not be commented on unless there's a specific issue or suggestion.
9. package.json:88
- Draft comment:
Bump tsdown to ^0.12.9. Ensure that the build process remains unaffected. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is about a dependency change, specifically bumping the version of 'tsdown'. The comment also asks to ensure that the build process remains unaffected, which is a request for confirmation or verification. According to the rules, comments on dependency changes and requests for confirmation or verification are not allowed.
10. package.json:92
- Draft comment:
Upgrade vitest to ^3.2.4 to benefit from recent bug fixes and improvements. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative and relates to a dependency change. It does not provide a specific suggestion or highlight a potential issue with the code.
11. package.json:96
- Draft comment:
In resolutions, update prettier to ^3.6.0 to align with the new dependency version. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is suggesting a change to a dependency version, which is related to dependencies. According to the rules, I should not comment on pure dependency changes or library versions that I don't recognize. Therefore, this comment should be removed.
12. package.json:97
- Draft comment:
Change Vite resolution to 'npm:rolldown-vite@^7.0.0' to enforce a consistent Vite version. Verify that this alias functions correctly with all Vite-related scripts. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =50%<= threshold50%The comment suggests a specific change to enforce a consistent Vite version, which is a valid suggestion. However, it also asks the author to verify that the alias functions correctly, which violates the rule against asking the author to ensure behavior is intended or tested. The first part of the comment is useful, but the second part is not allowed.
Workflow ID: wflow_qhzwGPn44Y7QCucl
You can customize
|
Deploy preview for stable-hash-x ready! ✅ Preview Built with commit f3cfd72. |
size-limit report 📦
|
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed f3cfd72 in 1 minute and 35 seconds. Click for details.
- Reviewed
89lines of code in3files - Skipped
0files when reviewing. - Skipped posting
3draft 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. .github/workflows/autofix.yml:34
- Draft comment:
The autofix-ci action version comment is updated to v1.3.2. Please confirm that the referenced digest and version label are intentional and secure. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
2. .github/workflows/ci.yml:16
- Draft comment:
Node version 18 has been removed from the CI matrix. If older Node versions are still supported (as per package engines >=12), consider adding Node 18 to the test matrix. - 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% The comment is speculative since it depends on information in package.json that I can't see. It's asking to "consider" something rather than pointing out a definite issue. The author likely removed Node 18 intentionally, and without seeing package.json, I can't verify if this is actually a problem. The comment could be valid if the package.json actually declares support for Node 18. I might be wrong to dismiss it without checking that file. Even if package.json does support Node 18, the PR author deliberately removed it, likely knowing the implications. Without strong evidence of a mistake, we should trust the author's judgment. Delete the comment because it's speculative and asks for consideration rather than pointing out a definite issue. The removal of Node 18 was likely intentional.
3. package.json:54
- Draft comment:
Multiple dependency updates (e.g. prettier, @vitejs/plugin-react-swc, vitest, and the resolution alias for vite) are applied. Please verify that these version bumps are fully compatible with your codebase and that the aliasing of 'vite' to 'rolldown-vite' meets your intended behavior. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
Workflow ID: wflow_3VOkGHnltz0GYGSe
You can customize
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.0.238->^0.0.2433.2.1->3.2.42891949->635ffb0^6.3.17->^7.0.0^6.3.5->^7.0.0Release Notes
microsoft/TypeScript-DOM-Lib-Generator (@types/web)
v0.0.243Compare Source
asynciterable.d.tsNo changes
index.d.tsNo changes
iterable.d.tsNo changes
v0.0.242Compare Source
asynciterable.d.tsNo changes
index.d.tsNo changes
iterable.d.tsNo changes
v0.0.241Compare Source
asynciterable.d.tsNo changes
index.d.tsNo changes
iterable.d.tsNo changes
v0.0.240Compare Source
asynciterable.d.tsNo changes
index.d.tsModified
textContenttextContenttextContenttextContenttextContenttextContentiterable.d.tsNo changes
v0.0.239Compare Source
asynciterable.d.tsNo changes
index.d.tsNew interfaces
CookieStoreManagerModified
cookiesNon-value types
"pointerrawupdate"onpointerrawupdateiterable.d.tsNo changes
vitest-dev/vitest (@vitest/coverage-v8)
v3.2.4Compare Source
🐞 Bug Fixes
vitest run --watchshould be watch-mode - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/8128 (657e8)--shard x/<count>exceeds count of test files - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/8112 (8a18c)minWorkerswhen onlymaxWorkersspecified - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/8110 (14dc0)task.metashould be available in custom reporter's errors - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/8115 (27df6)View changes on GitHub
v3.2.3Compare Source
🚀 Features
🐞 Bug Fixes
expect.anyreturn type - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/8129 (47514)process.send()- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/8125 (dfe81)View changes on GitHub
v3.2.2Compare Source
🚀 Features
🐞 Bug Fixes
createTesterscall on the main thread - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/8101 (142c7)vitest-browser-*packages - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/8103 (247ef)toEqual- by @dubzzz in https://github.com/vitest-dev/vitest/issues/8094 (02ec8)dotreporter to work in non interactive terminals - by @bstephen1 and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/7994 (6db9f)View changes on GitHub
vitejs/rolldown-vite (vite)
v7.0.0Compare Source
import.meta.urlin bundled Vite (#20235) (3bf3a8a), closes #20235ssrExportNameKey(#20266) (ac302a7), closes #20266normalizeModuleId(#20277) (9b98dcb), closes #20277configurePreviewServerhook (#20224) (b989c42), closes #20224configureServerhook (#20222) (f5cc4c0), closes #20222customResolver(#280) (de9074c), closes #280numberToPos(#20244) (3f46901), closes #20244vitejs/vite (vite)
v7.0.0Compare Source
import.meta.urlin bundled Vite (#20235) (3bf3a8a), closes #20235ssrExportNameKey(#20266) (ac302a7), closes #20266normalizeModuleId(#20277) (9b98dcb), closes #20277numberToPos(#20244) (3f46901), closes #20244Configuration
📅 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: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 dependencies including
viteand@vitest/coverage-v8, and adjust GitHub Actions workflows.viteto^7.0.0and@vitest/coverage-v8to3.2.4inpackage.json.@types/webto^0.0.243and@vitejs/plugin-react-swcto^3.10.2.autofix-ci/actionto635ffb0inautofix.yml.ci.yml.This description was created by
for f3cfd72. You can customize this summary. It will automatically update as commits are pushed.