build(deps-dev): Bump vite, @vitest/coverage-v8 and vitest in /web/admin - #612
Merged
Conversation
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
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 #607, whose dependabot branch conflicted after #608 (postcss) merged. Rather than hand-resolving a
package-lock.jsonconflict, this regenerates the lockfile fromdevwith 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 8npm test— 6 failed / 97 passed, byte-identical todevon vitest 3So 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