Skip to content

RELEASING.md

Latest commit

 

History

History
10 lines (8 loc) · 1.29 KB

RELEASING.md

File metadata and controls

10 lines (8 loc) · 1.29 KB
Raw

Releasing VoltHex

  1. Set a real GitHub remote and choose the permanent application identifier before the first public release.
  2. Generate an updater signing key with npm run tauri -- signer generate. Store the private key and password only in GitHub Actions secrets named TAURI_SIGNING_PRIVATE_KEY and TAURI_SIGNING_PRIVATE_KEY_PASSWORD.
  3. Add the updater plugin and its permissions, then configure plugins.updater.pubkey with the generated public key and plugins.updater.endpoints with the repository's latest.json URL. Enable bundle.createUpdaterArtifacts only after this configuration exists; Tauri deliberately rejects an incomplete updater configuration.
  4. Confirm package.json, src-tauri/Cargo.toml, and src-tauri/tauri.conf.json use the same version.
  5. Run the CI commands from the README and build both installers with npm run tauri -- build on a clean Windows runner.
  6. Push v<version>. The workflow creates a draft release. Install both artifacts on a clean Windows VM, exercise file paging/export, workspace recovery and a real mGBA connection, then publish the draft.

Authenticode signing is separate from Tauri updater signing. Configure a code-signing certificate in the Windows bundle settings or sign the produced installers in the release job before making them public.