Problem
The desktop workflow already builds a macOS DMG, but the public GitHub releases currently expose container assets only. That leaves macOS users needing to clone the repository and build the desktop app themselves.
Proposal
Publish the macOS desktop installer as a GitHub Release asset.
- Upload the Apple Silicon DMG produced by the desktop workflow to the corresponding release.
- Sign it with an Apple Developer ID certificate, notarize it with Apple, and staple the notarization ticket so Gatekeeper accepts the download without an unidentified-developer warning.
- Document the supported macOS architecture(s) and installation path in the release notes.
- Consider adding an Intel or universal build if that remains a supported target.
Context
I successfully built the existing desktop target on Apple Silicon. The current workflow already produces a DMG and verifies an ad-hoc signature, so this appears to be mainly a release-publishing and Apple signing/notarization integration task.
I would be happy to prepare a focused PR after maintainers confirm the preferred release trigger, asset naming, and how they want signing credentials managed.
Problem
The desktop workflow already builds a macOS DMG, but the public GitHub releases currently expose container assets only. That leaves macOS users needing to clone the repository and build the desktop app themselves.
Proposal
Publish the macOS desktop installer as a GitHub Release asset.
Context
I successfully built the existing desktop target on Apple Silicon. The current workflow already produces a DMG and verifies an ad-hoc signature, so this appears to be mainly a release-publishing and Apple signing/notarization integration task.
I would be happy to prepare a focused PR after maintainers confirm the preferred release trigger, asset naming, and how they want signing credentials managed.