Repository navigation
chore: upgrade dependencies and migrate Tauri runtime config - #80
Merged
Merged
Conversation
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.
Update frontend packages and the Rust dependency graph to current compatible releases, including React 19.3.1, Vite 8.3.5, Vitest/coverage 5.0.5, Tauri 2.12.5, tauri-build 2.7.4, and Tokio 1.54.1. Migrate the three getrandom calls to the 0.4 fill API. Keep windows-core on 0.62 because the current windows crate exposes those interface types.
Fix the STATIC_VCRUNTIME deprecation warning by pinning CLI 2.12.4 and configuring build.windows.staticVCRuntime. Reconcile the custom NSIS template with bundler 2.10.4 while preserving scoped process guards and replacement uninstallers. Update local build instructions and remove npm's ignored pnpm-only resolution-mode setting.
Validation: