Skip to content

Fix macOS signing, SVG logo CSP, and artifact names#7

Merged
johnmckenna-snd merged 1 commit intomainfrom
main.fix-signing-csp-artifact-names
Feb 11, 2026
Merged

Fix macOS signing, SVG logo CSP, and artifact names#7
johnmckenna-snd merged 1 commit intomainfrom
main.fix-signing-csp-artifact-names

Conversation

@johnmckenna-snd
Copy link
Contributor

What I Did

Fixed three build/release issues: macOS "damaged" error on unsigned apps, sndwrks logo not appearing in production builds due to CSP, and confusing architecture names in release artifacts.

What It Does

  • Ad-hoc signing (signingIdentity: "-" in tauri.conf.json): macOS no longer reports the app as "damaged". Users right-click → Open on first launch instead.
  • Vite asset inlining disabled (assetsInlineLimit: 0): The sndwrks logo SVG (3.8KB) was being inlined as a data: URL, which the CSP blocks. Now all assets are emitted as separate files.
  • Artifact renaming (new step in release.yml): Release filenames change from Conduit_0.1.0_aarch64.dmg to Conduit-0.1.0-mac-arm.dmg, etc.

Steps to Validate

  1. Run npx vite build — confirm sndwrks-logo-*.svg appears as a separate file in dist/assets/
  2. Verify src-tauri/tauri.conf.json is valid JSON
  3. On next release: confirm DMG opens without "damaged" error and artifacts have friendly names

Checklist

  • All unit tests passed locally
  • I tested what I did
  • I linted

…ck, rename release artifacts to user-friendly names
@johnmckenna-snd johnmckenna-snd merged commit 8eeb828 into main Feb 11, 2026
6 checks passed
@johnmckenna-snd johnmckenna-snd deleted the main.fix-signing-csp-artifact-names branch February 11, 2026 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant