feat: in-app updater with manual-download fallback#1298
Open
chrisbendel wants to merge 1 commit into
Open
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.
Description
As a user, clicking the "new version available" takes you to the latest github release page, requires you to manually download the application and reinstall it. This should provide a path to update to the latest version directly in your application without re-downloading 🤞. There may be some work on your end to make sure things work properly with the signing keys/etc.
I am happy to iterate on this with some feedback on your end too @CyberTimon, thanks for taking the time to check this out!
Type of Change
Changes Made
tauri-plugin-updater(Rust + JS), registered desktop-only.check→downloadAndInstall→relaunch); falls back to opening the releases page on any failure, so behavior is unchanged until updates are signed.updatercapability (excludes Android).TAURI_SIGNING_PRIVATE_KEY/_PASSWORDenv into the release build (no-op until secrets set).downloadingUpdatestring across all 12 locales.Not enabled by default — needs maintainer setup (one-time):
npx tauri signer generate→ add private key + password as repo secrets.createUpdaterArtifacts: trueandplugins.updaterendpoint intauri.conf.json.Until those land, CI builds exactly as before and the badge keeps opening the browser — zero regression.
Screenshots/Videos
Testing
Test Configuration:
Checklist
Additional Notes
Updater config (
createUpdaterArtifacts,plugins.updater.pubkey) is intentionally left out oftauri.conf.json— committing it without the signing key would fail the build. Happy to add it in this PR if you share a pubkey, or you can flip it on after merge.AI Disclaimer:
Open items on you:
cargo check/ build passes locally before checking the "no new warnings" box.