Skip to content

fix: allow unsigned macOS desktop releases - #20

Merged
aryanjsx merged 1 commit into
mainfrom
fix/macos-unsigned
Nov 1, 2026
Merged

aryanjsx merged 1 commit into
mainfrom
fix/macos-unsigned

Conversation

@aryanjsx

@aryanjsx aryanjsx commented Nov 1, 2026

Copy link
Copy Markdown
Owner

Summary

The desktop-v1.0.3 release built and published Windows and Linux, but the macOS job failed with "Apple signing secrets are required for release builds". As a result, verify-release and refresh-stable-channel were skipped, so desktop-latest/latest.json (the auto-update feed) was never published.

Changes

  • desktop.yml: release tag builds no longer fail on macOS when the Apple signing secrets are missing. They publish an ad-hoc signed, un-notarized build and log a warning. Updater artifacts are still signed with the Tauri key. Builds with APPLE_CERTIFICATE set still sign and notarize as before.
  • Docs: desktop download links on the home, Downloads and Installation pages pointed at nonexistent desktop-v1.0.2 files. They now link to the latest release, with a per-platform file table.
  • Docs: explain the macOS Gatekeeper and Windows SmartScreen prompts users see on first launch of unsigned builds.

Testing

  • desktop.yml parses as valid YAML.
  • mkdocs build succeeds, and the changed pages render with the new links.
  • The macOS build itself runs only in CI. The release path is exercised by the next desktop-v* tag.

After merge

Push desktop-v1.0.4 to publish all platforms, including the macOS .dmg, and refresh the desktop-latest update channel.

- Release tag builds no longer fail on macOS when Apple signing secrets
  are missing; they publish an ad-hoc signed, un-notarized build and log
  a warning. Updater artifacts are still signed with the Tauri key.
- Point desktop download links at the latest release instead of
  nonexistent desktop-v1.0.2 files.
- Explain the macOS Gatekeeper and Windows SmartScreen first-launch
  prompts for unsigned builds.
@aryanjsx
aryanjsx merged commit e309771 into main Nov 1, 2026
21 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.

1 participant