Repository navigation
In-app updates from GitHub releases - #44
Merged
Merged
Conversation
update.rs: update_info / update_check / update_install on tauri-plugin-updater (AppImage and .app through the plugin; Windows replaces the bare .exe itself). Updates are off in builds without KIVI_UPDATER_PUBKEY. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Account menu item and dot while an update waits, an update dialog with progress, Settings → Check for updates. The decisions (throttle, skip, switched off) are in update-check.js with a gjs test. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Updater files only when the signing key is set; Windows .exe signed with tauri signer; release job writes latest.json (tools/update_manifest.py) and marks tags with a suffix as pre-releases. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The headless tests' Tauri mock answers unknown commands with null, which made initUpdates throw an unhandled rejection and failed tests/smoke.sh on every page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI signed and published v0.2.90 on budenga/KiVi, and a local 0.1.0 macOS build updated itself to it. Linux, Windows and Intel macOS remain untested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
XyleMora
self-requested a review
November 22, 2026 18:45
XyleMora
approved these changes
Nov 22, 2026
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.
In-app updates
KiVi now looks for a newer GitHub release now and then, tells the user in the account menu, and on request downloads the file for their system, verifies its signature, replaces itself and restarts.
What the user sees
How it works
src-tauri/src/update.rs,tauri-plugin-updater2.x): commandsupdate_info,update_check,update_install. The feed ishttps://github.com/<repo>/releases/latest/download/latest.json, read from Rust (no REST API, so no 60/h limit; the CSP is untouched).releases/latestskips pre-releases.$APPIMAGE)..appfrom a signedKiVi_<v>_universal.app.tar.gz(one file for both architectures).install()would run the exe as an installer, so onlydownload()(which verifies) is used, andreplace_exeswaps the running exe (.exe.old, rolled back on failure, deleted at the next start).requireSignedVersionis on, so a doctored feed can't pair a new version number with an old file.src/desktop/updates.js(timers, dialog) andupdate-check.js(pure logic, tested under gjs). The last result is shared by all pages in localStoragekivi.updateCheck. Failures are never cached..app.tar.gzand the Windows.exe, and the release job writeslatest.jsonwithtools/update_manifest.py(all four platform entries or none). Tags containing-are published as pre-releases, so the updater skips them.Setup for this repository (maintainers)
Nothing changes until this is configured: without the key, builds work as before with updates off.
cargo tauri signer generate -w ~/.tauri/kivi.keyKIVI_UPDATER_PUBKEY= contents of~/.tauri/kivi.key.pubTAURI_SIGNING_PRIVATE_KEY= contents of~/.tauri/kivi.keyTAURI_SIGNING_PRIVATE_KEY_PASSWORD= its passwordKIVI_UPDATE_REPOis not needed here: it defaults toXyleMora/KiVi(a fork sets it to follow its own releases).v…). Builds made before this change can't update themselves; the first release with this change is the first one that can be updated from.Full details: README → Updates (developers),
docs/README.md→ Updates (users),CLAUDE.md→ Updates.Testing
cargo test(incl.replace_exeand its rollback),gjs -m tests/updates.js,python3 -m unittest tests/test_update_manifest.py; both new tests are added to the CI unit-test job.budenga/KiVi, with its own key: CI built and signed Linux, Windows and macOS and publishedv0.2.90with a completelatest.json. A local 0.1.0 macOS build (Apple Silicon) showed the notice, updated itself and restarted as 0.2.90.Notes for review
THIRD-PARTY-NOTICES.mdshows a large diff: 16 new crates (the updater and its dependencies), andtools/notices.pyrenumbers every licence-text reference after them. It's regenerated, and CI checks it with--check..gitignorenow ignores.DS_Store.🤖 Generated with Claude Code