Repository navigation
Clarify project maturity and patch Vite security advisories - #34
Merged
Merged
Conversation
styayur
changed the title
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.
State the overall Alpha project stage separately from feature-level verification and published release numbering. Replace the README wording "Latest stable release" with "Latest published release".
The existing frontend audit exposed high-severity Vite development-tool advisories. Update Vite 7.3.6 to the patched 7.3.7 release and regenerate its pnpm lock entries. No audit exemptions, implementation changes, license changes or historical release/tag changes are included.
Validation: the existing Windows/Linux builds, MSRV, frontend audit, Rust audit, secret scan and CodeForge regression gate must run on the updated head.