Skip to content

Automatic updates ​

Installed copies check https://github.com/skensell201/wiring/releases/latest/download/latest.json (plugins.updater.endpoints in src-tauri/tauri.conf.json, read by tauri-plugin-updater) 10 seconds after launch and every 6 hours (and, on macOS only, on Wiring → Check for Updates…; Windows has automatic checks only). pnpm tauri dev makes no automatic checks. That URL only resolves to the latest published release, so a draft is never offered: publishing the draft is the release gate.

An offered update shows Update X.Y.Z in the header. Install and restart downloads it, verifies its signature, installs it and relaunches; Later hides the offer until Wiring restarts or you check by hand. On Windows the update is the NSIS -setup.exe (the workflow sets updaterJsonPreferNsis), run in passive mode (plugins.updater.windows.installMode).

The dialog shows the release's notes before the install button, because an update is a decision and the decision needs to say what changes. The notes are the body of the GitHub release, and the workflow fills that body with the section of CHANGELOG.md for the tagged version. Write the notes before the tag: a release without them says so in the dialog.

Signing ​

Update packages are signed with Wiring's own updater key (minisign, made by pnpm tauri signer generate). This is separate from Apple / Windows code signing.

  • Public key: plugins.updater.pubkey in src-tauri/tauri.conf.json. Installed copies accept only packages signed by the matching private key.
  • Private key and its password: kept in ~/.tauri on the maintainer's machine and in the repository secrets TAURI_SIGNING_PRIVATE_KEY and TAURI_SIGNING_PRIVATE_KEY_PASSWORD. Never commit them. Keep an offline copy: if the key is lost, installed copies can no longer be updated and users must reinstall by hand.

The release workflow turns on bundle.createUpdaterArtifacts only when the key secret is set (it writes src-tauri/tauri.updater.conf.json and passes it with --config). Without the secret, such as on a fork, it warns and builds exactly as before with no update packages. Local builds (pnpm tauri build) need no key and produce no update packages.

Checking a release ​

  1. Run the workflow by hand (gh workflow run release.yml) and check the artifacts contain Wiring.app.tar.gz + .sig (macOS) and .msi.sig / -setup.exe.sig (Windows). latest.json appears only for a tagged run.
  2. Write the section for the version in CHANGELOG.md, tag vX.Y.Z, review the draft (it has latest.json), publish it.
  3. An installed earlier version shows Update X.Y.Z in the header within 10 s of its next launch.