Skip to content

build(deps-dev): Bump vite, @vitest/coverage-v8 and vitest in /web/admin - #612

Merged
filthyrake merged 1 commit into
devfrom
fix/607-vite-relock
Aug 18, 2026
Merged

build(deps-dev): Bump vite, @vitest/coverage-v8 and vitest in /web/admin#612
filthyrake merged 1 commit into
devfrom
fix/607-vite-relock

Conversation

@filthyrake

Copy link
Copy Markdown
Owner

Supersedes #607, whose dependabot branch conflicted after #608 (postcss) merged. Rather than hand-resolving a package-lock.json conflict, this regenerates the lockfile from dev with the bumped ranges applied.

Resolves to: vite 8.2.1, vitest 4.1.10, @vitest/coverage-v8 4.1.10 — and keeps the postcss bump from #608.

These are major bumps (vite ^6 → ^8, vitest ^3 → ^4) and the Python test suite does not exercise them, so I verified locally:

  • npm run build — succeeds on vite 8
  • npm test6 failed / 97 passed, byte-identical to dev on vitest 3

So the upgrade is not a regression. Worth knowing separately: those 6 admin test failures are pre-existing on dev, and no workflow currently runs the admin JS tests, which is why nobody has seen them.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Mrg8WVwMzMvNWVxeFAsgDK

Supersedes #607, whose branch conflicted after #608 (postcss) merged.
Rather than resolving a lockfile conflict by hand, regenerate
package-lock.json from dev with the bumped ranges applied.

Resolves to vite 8.2.1, vitest 4.1.10, @vitest/coverage-v8 4.1.10, and keeps
the postcss bump from #608.

Verified locally: `npm run build` succeeds on vite 8, and `npm test` gives
6 failed / 97 passed - identical to dev on vitest 3, so these major bumps
are not a regression. Those 6 failures are pre-existing, and no workflow
currently runs the admin JS tests.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mrg8WVwMzMvNWVxeFAsgDK
@filthyrake
filthyrake merged commit 32ae8dd into dev Aug 18, 2026
10 checks passed
@filthyrake
filthyrake deleted the fix/607-vite-relock branch August 18, 2026 00:15
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