Skip to content

fix: sign sparkle nested executables with secure timestamps - #34

Merged
joshuagruenstein merged 1 commit into
mainfrom
fix-sparkle-signing
Jul 14, 2026
Merged

fix: sign sparkle nested executables with secure timestamps#34
joshuagruenstein merged 1 commit into
mainfrom
fix-sparkle-signing

Conversation

@joshuagruenstein

Copy link
Copy Markdown
Member

Completes #33 — this part of the proven signing recipe was accidentally left uncommitted when #33 merged (caught before any release: build: cuts none).

Notarization rejected Sparkle's bare Autoupdate helper (not matched by the *.xpc/*.app find, and no --timestamp anywhere). Now signed inside-out per Sparkle's docs, timestamps on every invocation. This exact recipe passed the notary service locally: submission 9d83e166Accepted.

Merging this cuts the first signed + notarized release.

🤖 Generated with Claude Code

Notarization rejected the first submission over Sparkle's bare
Autoupdate helper (unsigned-by-us, no timestamp) — a find for *.xpc
and *.app misses a bare executable, and no codesign call carried
--timestamp. Sign Sparkle inside-out per its distribution docs with
timestamps everywhere. This exact recipe was verified against the
notary service: submission 9d83e166, status Accepted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@joshuagruenstein
joshuagruenstein merged commit 6d444f3 into main Jul 14, 2026
2 checks passed
@joshuagruenstein
joshuagruenstein deleted the fix-sparkle-signing branch July 14, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant