Emil_Shanaty/shacraft-launcher
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: bind AppImage updates to the running bundle

Browse Source
This commit is contained in:
Emil
2026-09-09 20:10:24 +03:00
parent b2ac174398
commit 696c6b0e52
4 changed files with 187 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/launcher-architecture.md
+5 -1
View File
@@ -220,7 +220,11 @@ The webview supplies no URLs, public keys, executable arguments, release version
or arbitrary file path. No generic updater plugin permission is granted to it.
The packaged native architecture selects the artifact: Windows preserves MSI
versus NSIS, macOS preserves Intel versus Apple Silicon, Linux only replaces an
AppImage. A Debian installation requires the user's package manager.
AppImage. The original non-symlink AppImage must have the expected native header,
and the frozen Tauri `APPDIR` must contain the actual running executable at
`usr/bin/shacraft-launcher`. Extracted binaries and inherited context from another
AppImage require manual installation. A Debian installation requires the user's
package manager.
Checks run once per application UI lifecycle and on explicit request. They do
not install automatically. The settings drawer shows installed/available