desktop-packaging

Packages Tauri v2 desktop apps into signed installers with auto-update via GitHub Releases.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill desktop-packaging-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desktop-packaging
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/desktop-packaging
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill desktop-packaging-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Taking a working Tauri desktop app to end users requires OS-specific installers, cryptographic signing, and a secure auto-update channel — a process that is easy to get wrong and dangerous to skip, since unsigned updates are an attack vector. ## Core Features & Use Cases - Per-OS Installers: Configures bundle.targets for Windows (MSI/NSIS), macOS (.dmg/.app), and Linux (.AppImage/.deb). - Signing & Auto-update: Generates the updater key pair with tauri signer generate, keeps the private key in CI secrets, and publishes signed artifacts plus latest.json to GitHub Releases via tauri-action. - Code Signing Guidance: Handles Windows Authenticode and macOS Developer ID notarization, or warns about SmartScreen/Gatekeeper "unknown publisher" prompts when certificates are absent. - Use Case: You have a tested Tauri app and want users on Windows and Linux to install it and receive verified automatic updates — this Skill configures the keys, CI workflow, and a test release proving the vN → vN+1 update path. ## Quick Start Use the desktop-packaging skill to generate the signed installers and set up auto-update via GitHub Releases for my Tauri app.

Frequently Asked Questions about desktop-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up auto-update for a Tauri v2 app?▼

Generate an updater key pair with `tauri signer generate`, put the public key in `tauri.conf.json`, store the private key and password as CI secrets, and point the updater `endpoints` at the `latest.json` published to GitHub Releases by `tauri-action`.

How to build Windows, macOS, and Linux installers for a Tauri app?▼

Declare the targets in `bundle.targets`: `msi` or `nsis` for Windows, `dmg` and `app` for macOS, and `appimage` or `deb` for Linux. A CI matrix build with `tauri-action` produces and signs each artifact.

Does Tauri auto-update work without code signing certificates?▼

Yes, the updater's own signature (the `.sig` files verified against the public key) works independently of OS code signing. Without an OS certificate, however, users will see SmartScreen or Gatekeeper "unknown publisher" warnings.

Why is my Tauri update failing signature verification?▼

Verification fails if the artifact was renamed after signing, the private key used differs from the public key in the config, or the `latest.json` does not match the published artifacts. Never rename artifacts after they are signed.

When should I use Velopack instead of the Tauri updater?▼

Use Velopack when the desktop app targets .NET/Avalonia rather than Tauri. Velopack handles packaging and delta auto-updates cross-platform for .NET apps, while the Tauri updater only applies to Tauri v2 projects.