Repository navigation
chore: upgrade Vite+ to 1.2.0 - #11
Merged
Merged
Conversation
thonatos
approved these changes
Oct 16, 2026
thonatos
left a comment
thonatos
left a comment
Member
There was a problem hiding this comment.
Reviewed the Vite+ 1.2.0 and Vitest 5 migration. Both CI checks pass, and a clean-worktree run of pnpm install --frozen-lockfile and pnpm verify also passed. The generated OpenAPI document is semantically unchanged after JSON normalization.
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
2 participants
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.
The workspace still uses
vite-plus@0.2.8andvitest@4.1.10. This change updates it tovite-plus@1.2.0and the bundledvitest@5.0.4, with matching Vite aliases and lockfile entries.The existing test and build commands remain available. Tests use the default mock lifecycle from Vitest 5. Shared packages keep their TypeScript source exports.
The OpenAPI generator formats its output without changing the document content. The change also records the migration in OpenSpec and applies consistent source and documentation formatting.