Skip to content

chore: bump vitest 3.2.7 -> 4.1.10 (Dependabot #5) - #31

Merged
alicoding merged 1 commit into
mainfrom
chore/vitest-4
Aug 12, 2026
Merged

chore: bump vitest 3.2.7 -> 4.1.10 (Dependabot #5)#31
alicoding merged 1 commit into
mainfrom
chore/vitest-4

Conversation

@alicoding

Copy link
Copy Markdown
Owner

Summary

  • Bumps vitest 3.2.7 -> 4.1.10 (Dependabot build(deps-dev): Bump vitest from 3.2.7 to 4.1.10 in /frontend #5, was green on Dependabot's own branch but still a major, deliberate pass per current dependency policy).
  • Checked peer compat before starting: vitest 4.1.10 peers on vite ^6||^7||^8, and Mill's frontend is already on vite 8.2.1 -- no vite cascade needed (the goal brief's hypothetical vite-5-forces-a-cascade scenario doesn't apply to this repo).
  • vite.config.ts's test block is a plain exclude array, no workspace config -- vitest 4's workspace -> projects rename doesn't touch anything here.
  • No source changes required -- package.json/package-lock.json only.

Test plan

  • npm run test -- 231/231 vitest tests pass (29 files; the jump from 227/28 is goal 0037's seedLifecycle.test.ts merging to main concurrently while this branch was in flight, confirmed by diffing the file list, not a vitest 4 behavior change)
  • npm run lint -- 0 errors, 4 pre-existing warnings
  • npx tsc --noEmit -- clean
  • npm run boundaries -- no dependency violations
  • npm run build -- production build succeeds
  • go vet . ./internal/..., go build (desktop + server tags) -- green
  • file-loc-limit, root-file-naming -- green
  • CI green through merge (auto-merge enabled)

🤖 Generated with Claude Code

https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft

Vitest 4 peers on vite ^6||^7||^8 -- Mill's frontend is already on
vite 8.2.1, so this is a clean, isolated bump with no vite cascade
(the hypothetical vite-5 scenario the goal brief flagged doesn't
apply here). vite.config.ts's `test` block is a plain `exclude` array
(no `workspace` config), so the workspace->projects rename in vitest
4 doesn't touch this repo either.

No source changes needed -- package.json/package-lock.json only.

Full local suite green: 231/231 vitest tests (29 files -- the jump
from 227/28 reflects goal 0037's seedLifecycle.test.ts merging to
main concurrently, not a vitest 4 behavior change, confirmed by
diffing the file list), eslint (0 errors, 4 pre-existing warnings),
tsc, boundaries, frontend build, go vet, go build (desktop+server),
file-loc-limit, root-file-naming.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
@alicoding
alicoding enabled auto-merge (squash) August 12, 2026 20:12
@alicoding
alicoding merged commit 3d278b6 into main Aug 12, 2026
16 checks passed
alicoding added a commit that referenced this pull request Aug 15, 2026
Vitest 4 peers on vite ^6||^7||^8 -- Mill's frontend is already on
vite 8.2.1, so this is a clean, isolated bump with no vite cascade
(the hypothetical vite-5 scenario the goal brief flagged doesn't
apply here). vite.config.ts's `test` block is a plain `exclude` array
(no `workspace` config), so the workspace->projects rename in vitest
4 doesn't touch this repo either.

No source changes needed -- package.json/package-lock.json only.

Full local suite green: 231/231 vitest tests (29 files -- the jump
from 227/28 reflects goal 0037's seedLifecycle.test.ts merging to
main concurrently, not a vitest 4 behavior change, confirmed by
diffing the file list), eslint (0 errors, 4 pre-existing warnings),
tsc, boundaries, frontend build, go vet, go build (desktop+server),
file-loc-limit, root-file-naming.


Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant