Skip to content

T-7270-polish-tauri-code-signing

Status: closed/obsoleted · Impact: medium · Complexity: medium

The polish desktop bundle (com.sksizer.vaultpolish) must be code-signed (and, on macOS, notarized) to be distributable without OS security warnings. The monorepo has no signing configuration or secrets for it. Establish the signing identity and wire it into the release build.

LocationRole today
apps/legacy-polish/src-tauri/tauri.conf.jsonidentifier: com.sksizer.vaultpolish; macOS entitlements set; no signing/notarization config
release pipelineno polish signing identity or secrets configured

Release builds produce signed (and notarized) bundles; signing identity and secrets are stored securely and referenced by the release job.

  1. Obtain the signing identity (owner-provided: Apple Developer ID cert + notarization credentials for macOS; equivalents for other targets).
  2. Add signing config to tauri.conf.json / the release environment.
  3. Store secrets securely (release-secret store) and reference them from the release job.

Requires owner-provided credentials — cannot be completed by an agent alone.

LocationKindChange
apps/legacy-polish/src-tauri/tauri.conf.jsonmodifybundle signing / notarization config
.github/workflows/modifysigning secrets wired into the release job
  • AC-1: a release build emits a signed bundle (verifiable via codesign/spctl on macOS or the platform equivalent).
  • AC-2: signing secrets are stored securely, not committed.
  • The release/versioning scheme itself (tracked in T-LH85).
  • T-LH85 — signing plugs into the release path.
  • Owner-provided signing credentials.
  • apps/legacy-polish/MIGRATION.md “Owner-gated remainder” item 5 (Tauri signing / bundle identifiers) — deferred at import.

← Back to Tasks