Skip to content

fix(release): disable mac notarization so unsigned builds don't fail CI - #40

Merged
JeanBaptisteRenard merged 1 commit into
mainfrom
fix/release-mac-unsigned
Jun 8, 2026
Merged

JeanBaptisteRenard merged 1 commit into
mainfrom
fix/release-mac-unsigned

Conversation

@JeanBaptisteRenard

Copy link
Copy Markdown
Collaborator

Follow-up to #39 (enabling fork releases).

Problem

package.json has build.mac.notarize: true. On a v* tag, the mac build job calls electron-builder which attempts Apple notarization. With no APPLE_ID / APPLE_APP_SPECIFIC_PASSWORD / APPLE_TEAM_ID secrets configured in repo settings, it errors out — blocking the entire release pipeline (linux + win included), not falling back to an unsigned build.

Fix

notarize: false so the first release produces green mac builds. Users get the usual Gatekeeper 'unidentified developer' prompt on first open; linux AppImage/deb and the auto-update feed are unaffected.

Flip back to true once the three Apple signing secrets are set in repo settings, if signed mac builds are wanted later.

Surfaced by the review of #39.

notarize:true makes electron-builder attempt Apple notarization on the
mac runner; with no APPLE_ID/APPLE_APP_SPECIFIC_PASSWORD/APPLE_TEAM_ID
secrets set it errors out and blocks the whole release pipeline rather
than falling back to an unsigned artifact. Set false so the first v*
tag produces green mac builds (Gatekeeper 'unidentified developer'
prompt on open). Flip back to true once the Apple signing secrets are
configured in repo settings.
@JeanBaptisteRenard
JeanBaptisteRenard merged commit 6d965b7 into main Jun 8, 2026
7 checks passed
@JeanBaptisteRenard
JeanBaptisteRenard deleted the fix/release-mac-unsigned branch June 8, 2026 18:53
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