Releases: kaikkone4/vire
Release list
Vire v0.8.1
Vire v0.8.1
First published GitHub Release. Reconciles version metadata 0.8.0 → 0.8.1 and enables the in-app update check (TASK-050/051) to resolve to a real state.
What's new:
- Version metadata reconciled across
Cargo.toml,tauri.conf.json, andCargo.lock. releases/latestnow returns200so "Check for updates" resolves to UpdateAvailable or UpToDate instead of Unknown.- No source, schema, CSP, or dependency change beyond version strings.
Download: Vire_0.8.1_aarch64.dmg (macOS, Apple Silicon / aarch64 only — Intel Macs are not supported) is attached to this release below.
Signing status: this build is unsigned and not notarized (ad-hoc/linker-signed only, no Developer ID). The long-term fix is Developer ID signing + notarization, tracked as TASK-028.
First launch — "Vire is damaged and can't be opened": if the DMG was downloaded through a browser, macOS tags it with a quarantine attribute, and on Apple Silicon, Gatekeeper will most likely block first launch with this "damaged" message. The app is not actually damaged — this is Gatekeeper's policy verdict for an unsigned, quarantined app, not file corruption.
If you hit this dialog, and you downloaded this DMG from this official release page (https://github.com/kaikkone4/vire/releases/tag/v0.8.1), and you trust the source: install Vire.app to /Applications, then run exactly:
xattr -dr com.apple.quarantine /Applications/Vire.appand open the app normally — it will launch without the workaround on every subsequent open. Only do this if both conditions above hold; if you're unsure where the DMG came from, don't run this.
Out of scope (deferred): signed + notarized build (TASK-028), in-app downloader/installer (TASK-042). No source, schema, CSP, or dependency change beyond version strings and this asset/notes update.