You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
macos: Releases are still not signed or notarized: configure the release credentials #2383
The macOS releases are still ad-hoc signed and not notarized. #630 wired signing and notarization into the release workflow (#669), and they run when the credentials are configured. They are not configured: in the release run of 2026-10-23 (39875589238), the Build macos arm64 job has codesign: false, codesignIdent: - and notarize: false. So every DMG since #669 is blocked by Gatekeeper on first start.
The release notes already explain the workaround (System Settings → Privacy & Security → Open Anyway, or xattr -dr com.apple.quarantine). That works, but every macOS user has to do it, and it teaches users to remove quarantine from apps.
What is needed
A maintainer decision and setup, no code:
An Apple Developer Program membership for the project (or a maintainer), for a Developer ID Application certificate.
The repository secrets that release-rust.yaml passes to .github/actions/setup-macos-codesigning: MACOS_SIGNING_IDENTITY, MACOS_SIGNING_CERT, MACOS_SIGNING_CERT_PASSWORD, MACOS_KEYCHAIN_PASSWORD, MACOS_SIGNING_PROVISIONING_PROFILE, MACOS_NOTARIZATION_USERNAME and MACOS_NOTARIZATION_PASSWORD (an app-specific password).
Acceptance criteria
The next release run shows codesign: true and notarize: true for both macOS jobs.
A downloaded DMG passes spctl --assess --type execute and xcrun stapler validate, and opens without the Gatekeeper prompt.
The release notes drop the Gatekeeper workaround for macOS.
Follow-ups this makes possible
A Homebrew cask in an obs-rust tap (brew install --cask), updated by the release workflow from SHA256SUMS. Without signing, a cask only replaces the download, not the Gatekeeper step, and as far as I know the official Homebrew cask repository does not take apps that fail Gatekeeper. (obs-rust/homebrew-tools holds only the contributors' formatter versions, so the cask would go in a new tap.)
The code side is done (#630/#669: release-rust.yaml signs and notarizes when the secrets exist). What's left is only the maintainer's to do: paying for an Apple Developer Program membership (money, an outside vendor, and an account tied to a person or organisation), then setting the seven MACOS_* repository secrets. No coordinator or contributor can do either.
Options:
Enrol and configure (recommended). Every macOS user stops needing the quarantine workaround, and it unblocks a Homebrew cask. About $99/year. An organisation enrolment needs a D-U-N-S number, an individual one doesn't.
Stay ad-hoc signed for the beta, keeping the documented workaround. Then lower this to P3 and say so in the release notes.
To answer: comment Decided: on the first line. P2, size:S once decided.
The maintainer renewed the Apple Developer Program (team NCFFSNX26D), and MACOS_SIGNING_IDENTITY is set. The remaining steps (the setup script, the other four secrets, and checking a signed release) are tracked in #2424.
Decided: enrol the Apple Developer Program and configure the macOS signing secrets (option 1). The maintainer took this decision on this issue in his comment of 2026-10-25 22:14 UTC, quoted verbatim:
The maintainer renewed the Apple Developer Program (team NCFFSNX26D), and MACOS_SIGNING_IDENTITY is set. The remaining steps (the setup script, the other four secrets, and checking a signed release) are tracked in #2424.
Re-posted in the Decided: form by the coordinator because the escalation comment above already carries the maintainer's answer but the automation only records a decision in this recognised shape. Nothing here is left for the maintainer to decide: the enrolment and the identity are done, the four remaining secrets are set (#2424, 2026-10-25 22:30 UTC), and a verify_only release run had both macOS builds Accepted and stapled (#2424, 2026-10-26 00:32 UTC).
Outstanding work is execution, not a decision, and it lives in the follow-up #2424: the next tagged/scheduled release has to show codesign: true / notarize: true, and the DMG has to pass spctl --assess + xcrun stapler validate. #2424 is blocked by #2432 (the macOS arm64 DMG shutdown crash), which is linked as a real GitHub dependency, so this issue is not waiting on the maintainer — it waits on that fix.
I am also removing the human-review-needed label by hand: the claim bot has no command that clears it once an escalation is answered, and leaving it on makes this issue report as "waiting on the maintainer" on every coordinator tick.
Triage: nothing here needs a worker of its own. Every remaining step is the follow-up #2424 (next release shows codesign: true / notarize: true, and the DMG passes spctl --assess + xcrun stapler validate), so I linked #2424 as a real GitHub dependency of this issue instead of leaving it in the triage list — it can only close after that one does, and #2424 is itself blocked by #2432 (the macOS arm64 DMG shutdown crash). No maintainer decision is outstanding.
Activity
zackees commentedon Oct 25, 2026
Triage → escalated to the maintainer.
The code side is done (#630/#669:
release-rust.yamlsigns and notarizes when the secrets exist). What's left is only the maintainer's to do: paying for an Apple Developer Program membership (money, an outside vendor, and an account tied to a person or organisation), then setting the sevenMACOS_*repository secrets. No coordinator or contributor can do either.Options:
To answer: comment
Decided:on the first line. P2, size:S once decided.zackees commentedon Oct 25, 2026
The maintainer renewed the Apple Developer Program (team NCFFSNX26D), and
MACOS_SIGNING_IDENTITYis set. The remaining steps (the setup script, the other four secrets, and checking a signed release) are tracked in #2424.zackees commentedon Oct 27, 2026
Decided: enrol the Apple Developer Program and configure the macOS signing secrets (option 1). The maintainer took this decision on this issue in his comment of 2026-10-25 22:14 UTC, quoted verbatim:
Re-posted in the
Decided:form by the coordinator because the escalation comment above already carries the maintainer's answer but the automation only records a decision in this recognised shape. Nothing here is left for the maintainer to decide: the enrolment and the identity are done, the four remaining secrets are set (#2424, 2026-10-25 22:30 UTC), and averify_onlyrelease run had both macOS builds Accepted and stapled (#2424, 2026-10-26 00:32 UTC).Outstanding work is execution, not a decision, and it lives in the follow-up #2424: the next tagged/scheduled release has to show
codesign: true/notarize: true, and the DMG has to passspctl --assess+xcrun stapler validate. #2424 is blocked by #2432 (the macOS arm64 DMG shutdown crash), which is linked as a real GitHub dependency, so this issue is not waiting on the maintainer — it waits on that fix.I am also removing the
human-review-neededlabel by hand: the claim bot has no command that clears it once an escalation is answered, and leaving it on makes this issue report as "waiting on the maintainer" on every coordinator tick.zackees commentedon Oct 27, 2026
Triage: nothing here needs a worker of its own. Every remaining step is the follow-up #2424 (next release shows
codesign: true/notarize: true, and the DMG passesspctl --assess+xcrun stapler validate), so I linked #2424 as a real GitHub dependency of this issue instead of leaving it in the triage list — it can only close after that one does, and #2424 is itself blocked by #2432 (the macOS arm64 DMG shutdown crash). No maintainer decision is outstanding.