fix(release): align the updater javascript plugin with the pinned rust crate - #32
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.
What changed
@tauri-apps/plugin-updaterback to2.10.1inpackage.jsonandbun.lockto match the pinnedtauri-plugin-updaterRust crate (workspace rev, crate 2.10.1).Why
The v0.4.3 release run failed on every platform leg at the Tauri CLI pre-build check: the dependency-bump train moved the JS plugin to 2.11.0 while the Rust side stays pinned at 2.10.1, and the CLI refuses to build on a minor mismatch. Release builds on
mainhave been broken since that bump. Aligning the JS side avoids touching the deliberately pinned Rust revision.Test plan
RUSTFLAGS="-D warnings" bun run tauri build --target aarch64-apple-darwin --no-bundlebuilds the release binary cleanly