4 Commits

Include renames

Author	SHA1	Message	Date
KeelrLeek	972dd103cb	release: 1.8.2-alpha	2026-09-10 07:19:18 -05:00
KeelrLeek	12fff9f6ad	setup, updater: the installer window was a dev build with nothing inside it, and latest never matched a prerelease ... Tauri decides dev-vs-production from the `custom-protocol` feature, not from --release, and both workflows build the setup exe with a plain `cargo build`. So cfg(dev) stayed on, the frontend was never embedded, and the window a tester opened loaded devUrl: "localhost refused to connect" on a blank 800x580. The feature is a default of the crate now, with a build.rs guard that fails a release build without it, and build.rs tracks setup/dist so a changed window cannot be left out of the binary it is supposed to be in. Behind that, the next wall: /releases/latest answers only with full releases, and every release here is an alpha, so it 404s. The setup app read that as a refused key and the app's Stable channel read it as a token that cannot see the repository — both have been broken since the first alpha. Each now lists /releases and takes the newest that is neither a draft nor the rolling nightly, which the list really does put first. And check_saved_key threw the saved key away on any failure at all, a dropped connection included. The entry it deletes is the app's own updater token, so only a refusal clears it now. The release notes name the file to hand a tester: six assets on the page and nothing saying which, while the bare NSIS installer is the biggest of them and installs with no key gate and no signature check.	2026-09-10 07:19:15 -05:00
KeelrLeek	3cfff93036	release: 1.8.1-alpha	2026-09-09 18:10:29 -05:00
KeelrLeek	f8508da081	setup: the installer is our own window — the alpha key is the gate, the release comes down with it and is verified before the silent install, and the in-app tour asks for the key too	2026-09-09 18:00:02 -05:00