Repository navigation
chore(deps-dev): bump vite from 5.0.12 to 6.4.4 in /ui-vue3 - #1604
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.0.12 to 6.4.4. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v6.4.4/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v6.4.4/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.4.4 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
AlexStocks
reviewed
Oct 24, 2026
AlexStocks
left a comment
AlexStocks
left a comment
There was a problem hiding this comment.
结论：可以合入，但有一个兼容性组合需要确认
这是 vite 从 5.0.12 到 6.4.4 的主版本升级，属于 dependabot 里风险最高的一类。
已核对
vite@6.4.4在 npm 上存在，engines为^18.0.0 || ^20.0.0 || >=22.0.0；CI 使用 Node 18，满足要求。- Head
093e8388的CI (ubuntu-latest - Go 1.23/1.24)均为 success，而该作业包含yarn install --frozen-lockfile && yarn build，说明当前组合确实能构建出dist/。 changed_files=2，实际 Diff 只有ui-vue3/package.json与ui-vue3/yarn.lock。
P2 · 插件生态没有同步升级
package.json 只改了 vite，没有动这两个强相关的依赖：
| 依赖 | 当前版本 | 对 vite 的 peer/依赖 |
|---|---|---|
@vitejs/plugin-vue |
^4.5.1 |
peer vite: ^4.0.0 || ^5.0.0 |
vitest |
^1.0.1 |
依赖 vite: ^5.0.0-beta.19 || ^5.0.0 |
升级后的 lockfile 里同时存在两份 vite：
vite@^5.0.0: version "5.0.12" # 由 vitest 引入
vite@^6.4.4: version "6.4.4" # 构建使用
Yarn 1 对 peer 冲突只告警、不失败，所以 CI 能过；但这是官方支持矩阵之外的组合。@vitejs/plugin-vue 5.x 才是声明支持 vite ^5 || ^6 的版本。建议在本 PR 内一并处理其一：
- 把
@vitejs/plugin-vue升到^5.2、vitest升到支持 vite 6 的版本；或 - 暂时把
vite固定在^5.4，等插件一起升级。
否则后续任何一次 minor 升级都可能在 vite build 或 vitest 里以难以归因的方式失败。
P3 · lockfile 的 registry 来源发生变化
本次新增条目的 resolved 使用 registry.yarnpkg.com，而仓库现有 lockfile 的分布是：
848 registry.npmmirror.com
84 registry.npmjs.org
6 registry.yarnpkg.com
CI 不受影响，但在依赖 npmmirror 的网络环境里，混合来源会让首次安装多走一次外网。可考虑统一。
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps vite from 5.0.12 to 6.4.4.
Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
5f0d9a4release: v6.4.4eec6464fix(server): check resolved ids for transform access (#20410)e570d8dfix(server): store ids tosafeModulePathsrather than URLs (#23656)8afec69fix(deps): update launch-editor to v2.14.2 (#23654)19902cffix(html): filename passed to transformIndexHtml should not include queries (...6c2c881release: v6.4.396b0c10fix: backport #22572, reject windows alternate paths (#22576)8fed5cffix(deps): backport #22571, reject UNC paths for launch-editor-middleware (#2...6b3fad0release: v6.4.2ca4da5dfix: avoid path traversal with optimize deps sourcemap handler (#22161)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vite since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.