Skip to content

feat: sign release builds when certificate secrets are set - #25

Merged
johnnyhuy merged 1 commit into
mainfrom
feat/signed-releases
Oct 6, 2026
Merged

johnnyhuy merged 1 commit into
mainfrom
feat/signed-releases

Conversation

@johnnyhuy

Copy link
Copy Markdown
Contributor

Summary

  • Pass Developer ID, Apple notarization, and Authenticode secrets into electron-builder. Missing secrets stay unset, so the current unsigned release path still publishes.
  • Add a Flatpak manifest under packaging/flatpak/ for a human Flathub submission. Flathub does not accept agent-opened pull requests.
  • Match the in-repo cask macOS floor to the binary (:monterey).

Consequences

  • Notarization still does not run until CSC_LINK, CSC_KEY_PASSWORD, and the APPLE_API_* secrets exist. This machine only has an Apple Development certificate, which cannot notarize a public DMG.
  • Windows signing waits on WIN_CSC_LINK and WIN_CSC_KEY_PASSWORD.

Testing

  • bun run test:unit (34 passed)
  • brew style on the cask is clean
  • brew audit --cask --new --online fails on signature (unsigned DMG) and GitHub notability, so no homebrew-cask pull request was opened

Made with Cursor

Developer ID and Authenticode secrets now reach electron-builder, with notarization when the Apple API key is present. A Flatpak manifest is included for a human Flathub submission, and the cask macOS floor matches the Electron binary.

Co-authored-by: Cursor <cursoragent@cursor.com>
@johnnyhuy
johnnyhuy merged commit d9eccd0 into main Oct 6, 2026
14 checks passed
@johnnyhuy
johnnyhuy deleted the feat/signed-releases branch October 6, 2026 12:54
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