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: Finish release signing: run the setup script, then verify a signed release (follow-up to #2383) #2424
Follow-up to #2383. The Apple side is ready, and one secret is set. What's left is listed below.
Done (2026-10-25)
Apple Developer Program renewed through 2026-10-25 → 2027-10-25. Team Zachary Vorhies (NCFFSNX26D).
MACOS_SIGNING_IDENTITY = Developer ID Application: Zachary Vorhies (NCFFSNX26D).
Setup script: gist. It makes the key and certificate request, takes the downloaded Developer ID certificate, builds the .p12, and sets the remaining secrets with gh secret set. No secret goes through chat.
It asks for the Apple ID email and opens the Developer ID Application certificate page (upload the request, download the .cer). Then it asks for an app-specific password from account.apple.com.
Back up ~/obs-rust-signing (private key and .p12) somewhere safe.
Coordinator: check that all five secrets are set: MACOS_SIGNING_IDENTITY, MACOS_SIGNING_CERT, MACOS_SIGNING_CERT_PASSWORD, MACOS_NOTARIZATION_USERNAME and MACOS_NOTARIZATION_PASSWORD. Then dispatch a release build of master.
Acceptance criteria
Both macOS jobs log codesign: true and notarize: true.
The DMG passes spctl --assess --type execute and xcrun stapler validate on a Mac, and opens without the Gatekeeper prompt.
The release notes drop the quarantine workaround (xattr / Open Anyway).
All five MACOS_* secrets are set (2026-10-25 22:30 UTC). The certificate is Developer ID Application: Zachary Vorhies (NCFFSNX26D), issued by Developer ID G2 and valid until 2027-11-24. It was checked against its key, and the .p12 uses legacy encryption so security import accepts it. Verification run (verify_only, publishes nothing): https://github.com/obs-rust/obs-studio/actions/runs/40240506753
Follow-up: the app-specific password was pasted into a chat log, so revoke it and set a new one once signing is confirmed (~/obs-rust-signing/set-notarization-secrets.sh).
Status: signing + notarization work. #2428 prints Apple's notary log; #2430 (merged) signs Sparkle's and CEF's nested code; verify_only run 40246027884: both macOS builds Accepted and stapled. Policy in #2433; reusable ci.yml section proposed in forge-ci/ci.yml#462. Left before closing this and #2383: the next tagged release shows codesign/notarize true and the quarantine workaround leaves the release notes. Still open for the account holder: rotate the app-specific password that was exposed in plain text.
Releases come from release-rust.yaml's daily schedule or a dispatch, not from tags pushed by hand, and it has failed since 2026-10-24: the Windows builds and the Windows x64 release gate. I dispatched a full release on master to get current evidence: run 40352480030.
Once a run publishes, check both macOS jobs show codesign: true and notarize: true, then run spctl --assess --type execute and xcrun stapler validate on the DMG on a Mac.
Triage: not Ready to hand to a worker yet — linked the open blocker as a real GitHub dependency (#2424 is now blocked by #2432, the macOS arm64 shutdown crash), so this leaves the triage list until that closes.
The release pipeline itself: release-rust.yaml has not published since 2026-10-23; every run since has failed. The current daily schedule run (40529110726, 15:15Z) is still in progress and already has Release gate / Fast Gate and Native macOS x86_64 DMG startup red. That failure is not tracked by an open issue, so it needs the maintainer's attention (the Windows builds and the Windows x64 release gate have been the failing jobs since 2026-10-24).
Final verification (spctl --assess --type execute, xcrun stapler validate on the DMG) still needs someone on a Mac — a verify-only run already produced an Accepted, stapled DMG on 2026-10-25 (run 40246027884), so this is confirmation, not new setup.
Signing credentials: the five MACOS_* secrets are set as organization secrets in obs-rust (repo-scope gh secret list only shows the two update keys), so the "run the setup script" step is done. Nothing here is a coordinator action until #2432 closes and the release lane goes green.
Triage update — the blocker from the last comment is closed and the pipeline item now has its own tracker, so what is left here is maintainer-side, and I am relabelling it rather than leaving it in the triage list.
So the acceptance criteria are down to two, and neither is worker-executable:
a publishingrelease-rust.yaml run on master at or after 25fc4bc6e in which the two macOS jobs log codesign: true and notarize: true — verify_only publishes nothing, so this is a maintainer dispatch;
spctl --assess --type execute and xcrun stapler validate on the produced DMG, plus opening it without the Gatekeeper prompt — needs a Mac.
There is no open decision and no code left to write here, which is why human-review-needed fits better than ready: a worker claim would stall on the two steps above. The signing credentials are already confirmed (five MACOS_* org secrets; a 2026-10-25 verify-only run produced an Accepted, stapled DMG), so this is confirmation and a publish, not setup. #2383 closes with it.
Answer with a Decided: comment, or just remove the label, when the publish and the Gatekeeper check are done.
Decided: the publish criterion is met; what is left is one Mac check plus the password rotation, both for the maintainer, in one sitting. Then close this and #2383.
Reasons:
Credentials are done: all five MACOS_* org secrets are set (comment of 2026-10-25 22:30Z), so the setup script needs no rerun.
A publishing release run on 25fc4bc6e already happened: run 40644942239 (workflow_dispatch, success) published v0.1.0-beta.20261028, built from 25fc4bc6e. Both Build macos arm64 🧱 and Build macos x86_64 🧱 log codesign: true and notarize: true, and The staple and validate action worked!. That is the first acceptance criterion, at the commit the 2026-10-28 triage named.
The Gatekeeper check needs a real Mac and a person, so no agent can do it. CI stapler validation is strong evidence, but the acceptance criteria ask for the Mac check, and it takes five minutes.
Maintainer, on a Mac:
gh release download obs-studio-rust-v0.1.0-beta.20261028 -R obs-rust/obs-studio -p "*macos-$(uname -m | sed s/x86_64/x86_64/).dmg" -D ~/Downloads
DMG=$(ls ~/Downloads/OBS-Studio-Rust-0.1.0-beta.20261028-macos-*.dmg)
xcrun stapler validate "$DMG"
hdiutil attach "$DMG" -mountpoint /Volumes/obsr
spctl --assess --type execute -vv /Volumes/obsr/*.app
open /Volumes/obsr/*.app # must open with no Gatekeeper prompt
hdiutil detach /Volumes/obsr
Download the DMG with a browser instead of gh if you want the quarantine attribute set, which is the real user path.
Then rotate the app-specific password that was pasted into a chat log (2026-10-25 comment): revoke it at account.apple.com, create a new one, and run ~/obs-rust-signing/set-notarization-secrets.sh.
If all of that passes, close #2424 and #2383. If spctl rejects the app, post its output here and this goes back to a worker.
Removing human-review-needed: no decision is left open, only the steps above.
The macOS release builds have been failing at notarization since 2026-11-13. This needs the Apple account holder, not a code change.
Both Build macos arm64 and Build macos x86_64 build and package the DMG, then the notary submission is refused:
Error: HTTP status code: 403. A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired.
Runs: the scheduled release of 2026-11-13 (run 43468991070), the manual run of 2026-11-14 11:45 UTC (43591511399) and the scheduled release of 2026-11-14 (43611475920). The 2026-11-12 and 2026-11-11 runs failed earlier for other reasons (Windows Tier 2, AppImage on 22.04), so they never reached notarization.
Fix: the account holder for team NCFFSNX26D signs in at developer.apple.com and accepts the updated Apple Developer Program License Agreement from the banner on the Account page. Apple shows it to the Account Holder role only. Then rerun the release workflow. The secrets and scripts need no change.
Activity
zackees commentedon Oct 25, 2026
All five
MACOS_*secrets are set (2026-10-25 22:30 UTC). The certificate isDeveloper ID Application: Zachary Vorhies (NCFFSNX26D), issued by Developer ID G2 and valid until 2027-11-24. It was checked against its key, and the .p12 uses legacy encryption sosecurity importaccepts it. Verification run (verify_only, publishes nothing): https://github.com/obs-rust/obs-studio/actions/runs/40240506753Follow-up: the app-specific password was pasted into a chat log, so revoke it and set a new one once signing is confirmed (
~/obs-rust-signing/set-notarization-secrets.sh).ci(macos): print Apple's notary log when notarization fails (#2424)
ci(macos): sign Sparkle's and CEF's nested code before notarizing (#2424
ci(macos): sign Sparkle's and CEF's nested code before notarizing (#2424
docs: macOS signing policy (#2424)
zackees commentedon Oct 26, 2026
Status: signing + notarization work. #2428 prints Apple's notary log; #2430 (merged) signs Sparkle's and CEF's nested code; verify_only run 40246027884: both macOS builds Accepted and stapled. Policy in #2433; reusable ci.yml section proposed in forge-ci/ci.yml#462. Left before closing this and #2383: the next tagged release shows codesign/notarize true and the quarantine workaround leaves the release notes. Still open for the account holder: rotate the app-specific password that was exposed in plain text.
ci(macos): print Apple's notary log when notarization fails (obs-rust…
ci(macos): sign Sparkle's and CEF's nested code before notarizing (ob…
docs: macOS signing policy (obs-rust#2424) (obs-rust#2433)
zackees commentedon Oct 26, 2026
What's left before this and #2383 close, after the coordinator's research:
release-rust.yaml's daily schedule or a dispatch, not from tags pushed by hand, and it has failed since 2026-10-24: the Windows builds and the Windows x64 release gate. I dispatched a full release on master to get current evidence: run 40352480030.codesign: trueandnotarize: true, then runspctl --assess --type executeandxcrun stapler validateon the DMG on a Mac.zackees commentedon Oct 27, 2026
Triage: not Ready to hand to a worker yet — linked the open blocker as a real GitHub dependency (#2424 is now blocked by #2432, the macOS arm64 shutdown crash), so this leaves the triage list until that closes.
State after the research above:
release-rust.yamlhas not published since 2026-10-23; every run since has failed. The current daily schedule run (40529110726, 15:15Z) is still in progress and already hasRelease gate / Fast GateandNative macOS x86_64 DMG startupred. That failure is not tracked by an open issue, so it needs the maintainer's attention (the Windows builds and the Windows x64 release gate have been the failing jobs since 2026-10-24).spctl --assess --type execute,xcrun stapler validateon the DMG) still needs someone on a Mac — a verify-only run already produced an Accepted, stapled DMG on 2026-10-25 (run 40246027884), so this is confirmation, not new setup.Signing credentials: the five
MACOS_*secrets are set as organization secrets in obs-rust (repo-scopegh secret listonly shows the two update keys), so the "run the setup script" step is done. Nothing here is a coordinator action until #2432 closes and the release lane goes green.zackees commentedon Oct 28, 2026
Triage update — the blocker from the last comment is closed and the pipeline item now has its own tracker, so what is left here is maintainer-side, and I am relabelling it rather than leaving it in the triage list.
What changed since 2026-10-27 17:24Z:
25fc4bc6e,verify_only=true, bothNative macOS arm64/x86_64 DMG startup 🧪success, with test(packaged-startup): Print crash-report evidence on a signal exit (#2714) #2718's crash-report capture armed and nothing printed.Build macos arm64 🧱success, DMG created and identity-verified) and the macOS release gates are green.So the acceptance criteria are down to two, and neither is worker-executable:
release-rust.yamlrun on master at or after25fc4bc6ein which the two macOS jobs logcodesign: trueandnotarize: true—verify_onlypublishes nothing, so this is a maintainer dispatch;spctl --assess --type executeandxcrun stapler validateon the produced DMG, plus opening it without the Gatekeeper prompt — needs a Mac.There is no open decision and no code left to write here, which is why
human-review-neededfits better thanready: a worker claim would stall on the two steps above. The signing credentials are already confirmed (fiveMACOS_*org secrets; a 2026-10-25 verify-only run produced an Accepted, stapled DMG), so this is confirmation and a publish, not setup. #2383 closes with it.Answer with a
Decided:comment, or just remove the label, when the publish and the Gatekeeper check are done.zackees commentedon Oct 30, 2026
Decided: the publish criterion is met; what is left is one Mac check plus the password rotation, both for the maintainer, in one sitting. Then close this and #2383.
Reasons:
MACOS_*org secrets are set (comment of 2026-10-25 22:30Z), so the setup script needs no rerun.25fc4bc6ealready happened: run 40644942239 (workflow_dispatch, success) published v0.1.0-beta.20261028, built from25fc4bc6e. BothBuild macos arm64 🧱andBuild macos x86_64 🧱logcodesign: trueandnotarize: true, andThe staple and validate action worked!. That is the first acceptance criterion, at the commit the 2026-10-28 triage named.Maintainer, on a Mac:
Download the DMG with a browser instead of
ghif you want the quarantine attribute set, which is the real user path.Then rotate the app-specific password that was pasted into a chat log (2026-10-25 comment): revoke it at account.apple.com, create a new one, and run
~/obs-rust-signing/set-notarization-secrets.sh.If all of that passes, close #2424 and #2383. If
spctlrejects the app, post its output here and this goes back to a worker.Removing
human-review-needed: no decision is left open, only the steps above.vpacher commentedon Nov 13, 2026
Coordinator triage: only maintainer steps are left, so this issue is not a worker task.
stapler validate,spctl --assess) on the newest beta DMG.Then close this issue and #2383. Labelled
human-review-needed, so the issue waits on the maintainer and leaves the triage list.rdoupe commentedon Nov 14, 2026
The macOS release builds have been failing at notarization since 2026-11-13. This needs the Apple account holder, not a code change.
Both
Build macos arm64andBuild macos x86_64build and package the DMG, then the notary submission is refused:Runs: the scheduled release of 2026-11-13 (run 43468991070), the manual run of 2026-11-14 11:45 UTC (43591511399) and the scheduled release of 2026-11-14 (43611475920). The 2026-11-12 and 2026-11-11 runs failed earlier for other reasons (Windows Tier 2, AppImage on 22.04), so they never reached notarization.
Fix: the account holder for team NCFFSNX26D signs in at developer.apple.com and accepts the updated Apple Developer Program License Agreement from the banner on the Account page. Apple shows it to the Account Holder role only. Then rerun the release workflow. The secrets and scripts need no change.