chore: remove tauri updater plugin#29
Merged
Merged
Conversation
The TAURI_SIGNING_PRIVATE_KEY secret was never configured, so Windows and Linux Release builds failed at the signing step with "Missing comment in secret key". Since auto-update is not in use, drop the plugin entirely instead of generating a key. - Remove tauri-plugin-updater and tauri-plugin-process (only needed for relaunch) from Cargo.toml / package.json - Remove updater plugin registration, background check, and frontend updater module - Drop the Software Update section from Settings (version is still shown at the bottom of the view) - Strip TAURI_SIGNING_* env and includeUpdaterJson from release.yml Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
failed to decode secret key: incorrect updater private key password: Missing comment in secret key. Root cause is thatTAURI_SIGNING_PRIVATE_KEY/_PASSWORDGitHub Secrets were never set, whilecreateUpdaterArtifacts: trueandincludeUpdaterJson: truewere forcing the signing step.Changes
tauri-plugin-updaterandtauri-plugin-process(only used forrelaunch) fromCargo.tomlandpackage.jsoncheck_for_update_backgroundfromsrc-tauri/src/lib.rsupdater:default/process:allow-restartcapabilities and theplugins.updaterblocks fromtauri.conf.json/tauri.windows.conf.jsonsrc/lib/updater.tsand the Software Update section in Settings. Current version is still shown at the bottom of the Settings view.TAURI_SIGNING_*env vars andincludeUpdaterJson/updaterJsonPreferNsisfrom.github/workflows/release.ymlsoftwareUpdate,checkForUpdates,updateAvailable*,downloadAndInstall,installingUpdate,updateInstalledRestarting,updateFailed,upToDate,currentVersion,retry)Test plan
pnpm build(tsc + vite) — cleanpnpm test— 3/3 passcd src-tauri && cargo test— 48/48 passcd src-tauri && cargo clippy— no warningsReleaseworkflow passes on all three platforms🤖 Generated with Claude Code