What problem does this solve in your TCC permission workflow?
Unsigned or non-notarised builds trigger Gatekeeper warnings on first launch, which adds friction for non-technical users. Publishing through Homebrew Cask would also make installation and upgrades easier.
What behaviour do you want?
Notarise release builds so Gatekeeper warnings are reduced for end users, then publish a Homebrew Cask once the signed/notarised distribution flow is stable.
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This improves how users install and trust the app they already run locally. It does not change the product’s local-first behavior; it improves distribution and onboarding.
Scope check
Please confirm this request fits the project scope in CONTRIBUTING.md. This affects packaging and distribution, not network dependency in the app itself and not writes to system TCC files.
Additional context
A good outcome would be a repeatable release workflow that covers signing, notarisation, stapling, and whatever metadata is needed for a future Homebrew Cask submission.
What problem does this solve in your TCC permission workflow?
Unsigned or non-notarised builds trigger Gatekeeper warnings on first launch, which adds friction for non-technical users. Publishing through Homebrew Cask would also make installation and upgrades easier.
What behaviour do you want?
Notarise release builds so Gatekeeper warnings are reduced for end users, then publish a Homebrew Cask once the signed/notarised distribution flow is stable.
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This improves how users install and trust the app they already run locally. It does not change the product’s local-first behavior; it improves distribution and onboarding.
Scope check
Please confirm this request fits the project scope in
CONTRIBUTING.md. This affects packaging and distribution, not network dependency in the app itself and not writes to system TCC files.Additional context
A good outcome would be a repeatable release workflow that covers signing, notarisation, stapling, and whatever metadata is needed for a future Homebrew Cask submission.