Repository navigation
Notarize releases with a Developer ID - #14
Merged
Merged
Conversation
Releases are now signed with a Developer ID Application certificate and notarized by Apple, so the install docs and the Homebrew cask no longer tell people to choose Open Anyway. The getting-started page says that copies up to 0.1.6, signed with the old self-signed certificate, can't install a notarized version themselves and need one download by hand. Apple took close to half an hour over the first submission, and notarytool's 30-minute wait gave up just before it answered, so release.sh now waits up to 90 minutes for each submission and the release job has room for both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
srozen
force-pushed
the
notarized-releases
branch
from
November 8, 2026 10:26
508482a to
aada0ac
Compare
srozen
changed the title
…fore saving it Since GitHub's macOS 26 runners moved to macOS 26.7, zsh sometimes takes more than 15 seconds to start while the whole suite runs, and different zsh tests failed from run to run: one timed out waiting for its first command although the shell ran it a moment later. The wait helpers now allow 60 seconds when CI is set. They return as soon as their condition holds, and no test waits for one to time out, so this only costs time when a test fails. Keeping panes also had a race of its own: a command's output is kept once the prompt after it is drawn, which can come just after the pane is back at the command line, so the test could save the pane before the output of seq 1 5 was in its timeline. It now waits for that output. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases are now signed with a Developer ID Application certificate and notarized by Apple. The secrets are set, and a local 0.1.7 build passed notarization for both the app and the disk image.
docs/getting-started.mdand the cask's caveats. Getting started now says that copies up to 0.1.6, signed with the old self-signed certificate, can't install a notarized version themselves and need one download by hand (orbrew upgrade).scripts/release.shnow waits up to 90 minutes per submission, and the release job's limit goes from 75 to 210 minutes to fit both.Checked locally:
swift build --build-tests,swift test(346 tests passed) and the universalscripts/build-app.sh release.🤖 Generated with Claude Code