Repository navigation
chore(deps-dev): bump vitest, vite and api-extractor in one batch - #48
Merged
Merged
Conversation
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 Co-Authored-By: htjulia <htjulia1@gmail.com>
This was referenced Oct 6, 2026
htcom-code
added a commit
that referenced
this pull request
Oct 12, 2026
…ch (#54) Dependabot opened two patch updates: #52 (vite 8.3.2 to 8.3.3 and @vitejs/plugin-react 6.1.1 to 6.1.2, demo) and #53 (@microsoft/api-extractor 7.59.3 to 7.59.4, the dev group). Both rewrite pnpm-lock.yaml, so whichever lands first leaves the other conflicting; they land as one branch, as #48 and #50 did. The lockfile is the union of what the two pull requests resolved; git merged it without conflicts. vite takes postcss 8.5.29 while the Vue compiler stays on 8.5.28, so both versions remain, as #52 had it. Nothing here reaches a published package: every change is in devDependencies and pnpm api reports all five API reports unchanged. Closes #52 Closes #53 Tags: #deps
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.
Supersedes #45 (vitest group), #46 (vite group) and #47 (dev group:
@microsoft/api-extractor).Why one branch
All three pull requests rewrite
pnpm-lock.yaml, and #45 and #46 conflict outright: vitest'ssnapshot keys carry vite's version as a peer suffix (
…(vite@8.3.0…)), so each side rewrites theother's lines. Merged in sequence, the second and third would land on a lockfile that moved under
them, so they go in as one squash.
What moves
vitest,@vitest/browser,@vitest/browser-playwright(root dev)vite(demodev)@microsoft/api-extractor(root dev)All patch releases, all
devDependencies. Nothing here reaches a published package.pnpm apireports all five API surfaces unchanged.The lockfile is the union of the three pull requests, not a fresh resolve
Newer patches are already out (
vitest5.0.3,vite8.3.2,api-extractor7.59.4), and are-resolve picks them up:
pnpm install --lockfile-onlyon the vitest side movedviteto8.3.2 and
rolldownto 1.2.12. That would ship versions no pull request reviewed, so the conflictwas resolved by hand instead: keep the vitest side and rewrite its vite peer suffix from 8.3.0 to
8.3.1.
Checked mechanically: the set of
packages:entries equals main with each pull request'sadditions and removals applied, with nothing missing and nothing extra. Transitive steps come
along as the pull requests resolved them (
rolldown1.2.11,magic-string1.4.2,std-env4.3.0,
@rushstack/node-core-library5.25.0, …).siginfoandstackbackdrop out withvitest 5.0.2.
Verification
pnpm install --frozen-lockfilepasses, and plainpnpm installleaves the tree cleanpnpm check: build, per-package checks, test typecheck, 391 tests passpnpm test:browser: 477 tests pass (run locally as well as in the CIbrowserjob, sincethis moves vitest's browser runner)
pnpm api: all 5 API reports matchpnpm api:docs: typedoc generates