Skip to content

Build an unsigned macOS app when signing secrets aren't set - #2

Merged
RealAct merged 1 commit into
mainfrom
claude/fix-macos-release
Oct 13, 2026
Merged

RealAct merged 1 commit into
mainfrom
claude/fix-macos-release

Conversation

@RealAct

@RealAct RealAct commented Oct 13, 2026

Copy link
Copy Markdown
Owner

Before: the v0.1.0 release build failed on macOS with "failed to import keychain certificate", so the release has the .deb, AppImage and .msi but no .dmg.

After: with no Apple signing secrets set, the macOS job builds an unsigned .dmg instead of failing. Once the secrets are added, it signs and notarizes as before.

The Release workflow can also be started by hand from the Actions tab with a tag name, so the missing .dmg can be added to the existing v0.1.0 release without a new tag.

How: the Apple variables used to be passed to tauri-action as empty strings, which the bundler treats as "sign with this certificate". A new step exports them only when APPLE_CERTIFICATE is set. workflow_dispatch gets a required tag input, used as the release tag when present.

🤖 Generated with Claude Code

https://claude.ai/code/session_013wWY5SvB2w46Qw92qtHG5e


Generated by Claude Code

An empty APPLE_CERTIFICATE made the bundler try to import a certificate and
fail. Also let the Release workflow be re-run by hand for an existing tag.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_013wWY5SvB2w46Qw92qtHG5e
@RealAct
RealAct merged commit e6eec13 into main Oct 13, 2026
5 checks passed
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.

2 participants