Repository navigation
fix: align Tauri versions for desktop releases - #112
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
1 participant
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 v1.12.1 desktop release build stops before compilation because the npm lockfile resolves @tauri-apps/api 2.12.3 and plugin-dialog 2.8.2 while Cargo resolves Tauri 2.11.0 and dialog 2.7.1. The Tauri CLI requires matching major/minor versions; cargo check alone does not enforce this.
Restore the npm versions requested by the original Dependabot PRs: API 2.11.1 and dialog 2.7.1. Keep the other compatible security fixes. Upgrade desktop CI on all three platforms to a full Tauri debug build without installer bundling, using the locked Cargo resolution, so this mismatch fails before a release is tagged.
Validation: all 647 tests, ESLint, actionlint, and npm production audit passed. The full local Tauri debug build passed. CI also builds the executable successfully on Linux, macOS and Windows.
The v1.12.1 tag remains unchanged. The corrected desktop release will be v1.12.2.