Repository navigation
chore(deps-dev): bump vite from 8.3.1 to 8.3.2 in the vite group across 1 directory - #46
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
htcom-code
added a commit
that referenced
this pull request
Oct 6, 2026
Dependabot opened three patch updates: #45 (vitest group 5.0.1 to 5.0.2), #46 (vite 8.3.0 to 8.3.1, demo) and #47 (`@microsoft/api- extractor` 7.59.2 to 7.59.3, the dev group). All three rewrite `pnpm-lock.yaml`, and #45 and #46 conflict directly because vitest's snapshot keys carry vite's version as a peer suffix, so they land as one branch. The lockfile is the union of what the three pull requests resolved. A fresh resolve would have pulled vite 8.3.2 and rolldown 1.2.12, which no pull request carried; the conflict was resolved by keeping the vitest side with its vite peer suffix moved to 8.3.1. The package set matches main plus each pull request's additions and removals exactly, and `pnpm install --frozen-lockfile` accepts it. Nothing here reaches a published package: every change is in devDependencies, and `pnpm api` reports all five API reports unchanged. Tags: #deps
Bumps the vite group with 1 update in the / directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 8.3.1 to 8.3.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.3.2/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 8.3.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/vite-1a5240e55e
branch
from
October 6, 2026 02:36
75c3da6 to
84777fa
Compare
htcom-code
added a commit
that referenced
this pull request
Oct 6, 2026
Dependabot opened three patch updates: #45 (vitest group 5.0.2 to 5.0.3), #46 (vite 8.3.1 to 8.3.2, demo) and #49 (`@types/node` 26.6.3 to 26.6.4, the dev group). vitest's snapshot keys carry both vite's and `@types/node`'s versions as peer suffixes, so each pull request rewrites the same lockfile lines and they land as one branch. The lockfile is the union of what the three pull requests resolved. Re-resolving the peer suffixes left four transitive packages behind (`rolldown`, `@oxc-project/types`, `chai`, `tinyrainbow`); a targeted update moved them to the pull requests' versions. #46 moves only postcss's `source-map-js` edge to 1.2.2, which `pnpm update` cannot express, so that entry was copied from its lockfile. The package set matches main plus each pull request's changes exactly. `why-is-node-running` steps back to 3.2.1 because vitest 5.0.3 pins it exactly. Nothing here reaches a published package: every change is in devDependencies and `pnpm api` reports all five API reports unchanged. Tags: #deps
Contributor
Author
|
Looks like vite is no longer updatable, so this is no longer needed. |
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 the vite group with 1 update in the / directory: vite.
Updates
vitefrom 8.3.1 to 8.3.2Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
1003321release: v8.3.2 (#23623)24bd331fix(worker): align worker urls in client and server when using terser (#23614)94d0080perf: only register time middleware when debug logging is enabled (#23621)89574f6perf: avoid encoding intermediate source maps (#23461)5a3a010fix(server): release previous environments after initialization (#23499)1929b4cdocs: fix dead og-image PNG links in vite6/vite7 changelog entries (#23594)6894f5cfix(server): handle file watcher errors without crashing (#23503)cf5c028perf(build): avoid quadratic link scan in the preload helper (#23510)bba3bb8fix: mergebuild.rolldownOptions.output.minifycorrectly (#23536)5e4b9cafix(optimize-deps): avoid "unsupported" warnings for browser:false mappings (...