Notarised builds and submission to official Homebrew

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
39/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
devops, release

Research direction

Start with the release workflow and scripts/build.sh, where WISP_SIGN_IDENTITY is already supported. Check how releases build and package the DMG, then determine how to sign, notarise and staple it; done means macOS opens the app without first-launch approval. Official Homebrew submission is a later step once its notability criteria are met.

Written by the indexing model from the issue text.

Description

enhancement

Sign the app with a Developer ID certificate and notarise it, so macOS opens it without the first-launch approval.

Plan: sign and notarise in the release workflow (WISP_SIGN_IDENTITY is already supported by scripts/build.sh), staple the DMG, then submit the cask to official Homebrew once its notability criteria are met. Until then Wisp ships through its own tap and an ad-hoc signed DMG.

Dominant language
Swift
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from karanzykx/wisp

All issues in karanzykx/wisp

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.