-
Guará 1.3.3
StableCI / Format and clippy (push) Successful in 2m46sCI / Dependency audit (push) Successful in 11sCI / Check desktop app (Linux) (push) Successful in 4m9sCI / Tests (Linux) (push) Successful in 8m6sRelease / Create release (push) Successful in 8sRelease / CLI (linux-aarch64) (push) Successful in 2m35sRelease / CLI (linux-x86_64) (push) Successful in 3m21sRelease / Desktop app (linux-aarch64) (push) Successful in 6m37sRelease / Desktop app (linux-x86_64) (push) Successful in 12m16sRelease / Desktop app (windows) (push) Successful in 9m40s
gitea-actions
released this
2026-10-31 10:13:21 +00:00 | 5 commits to main since this releaseUnified updater architecture with Sabiá: migrated from the signed
tauri-plugin-updaterto direct Gitea Releases API checking and self-updating with SHA-256 verification.Changed
- New update mechanism: The updater was rewritten to match Sabiá's model. Updates now query the Gitea Releases API directly, verify package checksums via
.sha256, and no longer rely onlatest.jsonor minisign updater keys. - CLI self-update (
guara update): The CLI now supportsguara update(checks for new versions) andguara update --apply(downloads, verifies SHA-256 checksum, and atomically replaces the binary). - Desktop app notice: The desktop app checks Gitea on startup and links directly to the new release packages.
- Important notice for existing installations: Versions up to 1.3.2 used the previous signed
tauri-plugin-updatermechanism looking forlatest.json. Because that mechanism has been retired, existing installs will not automatically find version 1.3.3: download version 1.3.3 once manually from Gitea Releases, and future update checks will work through the new unified mechanism. - Removed
tauri-plugin-updaterdependency,createUpdaterArtifactsconfiguration, and theupdater(Build latest.json) CI job.
Downloads
- New update mechanism: The updater was rewritten to match Sabiá's model. Updates now query the Gitea Releases API directly, verify package checksums via