Repository navigation
build(deps-dev): bump vite from 8.0.16 to 8.1.6 - #418
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 8.0.16 to 8.1.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v8.1.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.1.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.1.6 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
| "vite@npm:^8.0.16": | ||
| version: 8.0.16 | ||
| resolution: "vite@npm:8.0.16" | ||
| version: 8.3.5 | ||
| resolution: "vite@npm:8.3.5" |
There was a problem hiding this comment.
🟡 (optional) Merging installs vite 8.3.5, not the 8.1.6 the title and changelog describe, so reviewers approve a version nobody has vetted. The vite@ npm:^8.0.16 entry resolves to version: 8.3.5 with the 8.3.5 checksum. That adds two minor releases of unreviewed changes, plus rolldown ~1.2.14 and a new @ vitejs/devtools peer range of ^0.7.1 || ^0.8.0. Fix: regenerate the lockfile so the vite entry resolves to 8.1.6, or retitle the PR and review the 8.2/8.3 changelogs before merging.
Why this was flagged
yarn.lock:1588-1590 maps the vite@ npm:^8.0.16 descriptor to resolution: "vite@ npm:8.3.5". The PR title and quoted release notes only go up to 8.1.6. With yarn install --immutable, CI and every developer install 8.3.5, while the base installs 8.0.16. The 8.2.x and 8.3.x changes are not in the PR's changelog. They include the rolldown 1.0.3 -> 1.2.15 bump (yarn.lock:1374), @ oxc-project/types =0.155.0, and the changed @ vitejs/devtools peer range at yarn.lock:1600. So the review covered less than what merges. package.json:54 ("vite": "^8.0.16") allows this, so nothing stops it.
Verification: The trigger is any yarn install (including --immutable in CI) on the merged lockfile. That install gets vite 8.3.5, but the PR title "bump vite from 8.0.16 to 8.1.6" and the quoted changelog stop at 8.1.6. On HEAD this is yarn.lock:1588-1590. package.json:54 still has "vite": "^8.0.16", so the 8.3.5 resolution is valid for that range.
|
@SocketSecurity ignore-all |
Bumps vite from 8.0.16 to 8.1.6.
Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
dade886release: v8.1.6170b927fix(server): store ids tosafeModulePathsrather than URLs (#23656)e46fc9cfix(deps): update launch-editor to v2.14.2 (#23654)4ff2522fix(html): filename passed to transformIndexHtml should not include queries (...5e7fe12release: v8.1.56c08c39fix(optimizer): respect importer module format for dynamic import interop wit...5a72b87fix(client): overlay error message format align rolldown (#22869)f8b38e3fix(module-runner): don't crash stack-trace source mapping when globalThis.Bu...8100320fix(bundled-dev): avoid duplicatedbuildEnd(#22931)c88c236docs(build): fix incorrect@defaultfor build.cssMinify (#22948)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.