Alan Wizemann
868e61979e
Drafts skip the appcast push and main tag, so a draft release won't show up in users' Sparkle update feed and v1.6.0 stays "latest" until explicitly promoted. The signed appcast entry is saved to the release dir for later manual promotion. Also adds release notes file convention: releases/v<VERSION>/RELEASE_NOTES.md is auto-included in the version-bump commit and used as the GitHub release body. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.5 KiB
What's New in 1.6.1
Auto-updates
Scarf now ships with Sparkle. On launch (and daily thereafter) it checks an EdDSA-signed appcast at awizemann.github.io/scarf/appcast.xml. When a new version is available you'll get an in-app update prompt — no more manually downloading zips and dragging into Applications.
You can disable automatic checks or trigger a manual one from Settings → General → Updates, the menu bar icon, or the Scarf → Check for Updates… menu item.
Notarized & Developer ID signed
This is the first release that's properly Developer ID signed and notarized by Apple. Gatekeeper accepts it on first launch — no more right-click → Open dance, no more "Scarf cannot be opened because the developer cannot be verified" warnings.
Fixes
- Chat works correctly when no terminal hermes session is running, and surfaces the real error when it can't reach the agent (b6df…)
Under the hood
- Tracked
Info.plist(replacing auto-generation) so signing-relevant keys live in version control - New
UpdaterServicewraps Sparkle and is injected via SwiftUI.environment() - One-command release pipeline at scripts/release.sh handles archive → sign → notarize → staple → appcast → GitHub release → tag
Migrating from 1.6.0: unzip and replace your existing Scarf.app in /Applications. After this release, future updates install in-place via Sparkle.