Release Kaze

Release Kaze

This skill releases new versions of Kaze using a Go CLI in this repo (cmd/kaze-release). The CLI can run fully automated and non-interactively, so a release can be triggered directly from a chat session.

There are two modes:

• Full auto (-build) - archive, export (Developer ID), notarize, staple, package, sign, and publish. Nothing in Xcode's GUI is required.
• Package-only (no -build) - assumes the user already exported a notarized ~/Downloads/Kaze.app from Xcode, then packages & publishes.

Prefer full auto unless the user says they've already exported the app.

Publishing is outward-facing (GitHub release, appcast that existing users' Sparkle reads). Confirm the version, build number and notes with the user before running it.

Prerequisites

Always required:

1. Tools installed: create-dmg (brew), gh (GitHub CLI, authenticated), git, plutil, go.
2. The Sparkle sign_update binary in DerivedData (created when the project is built/archived - the -build flow produces it automatically).

For full auto (-build) additionally:

3. xcodebuild, xcrun, ditto (all part of Xcode).
4. A notarytool keychain profile. The CLI defaults to kaze-notary. Notary credentials belong to the Apple developer account, not the app, so the profile already used for Screendrop works too: -notary-profile screendrop-notary. To create a dedicated one:

   xcrun notarytool store-credentials "kaze-notary" \
     --key /path/to/AuthKey_XXXXXXXXXX.p8 --key-id XXXXXXXXXX --issuer <issuer-uuid>

The Release CLI

Source: /Users/fayazahmed/Developer/fayazara/mac/Kaze/cmd/kaze-release/

Flags

• -build - run the archive → export → notarize → staple phase first.
• -set-version <x.y.z> - set MARKETING_VERSION before archiving (and commit it). Used with -build.
• -set-build <n> - set CURRENT_PROJECT_VERSION before archiving (and commit it). Used with -build.
• -scheme <name> - Xcode scheme to archive (default Kaze; never Kaze Dev).
• -notes "<text>" - release notes, one bullet per line (markdown - prefixes are stripped). Skips the interactive prompt.
• -notes-file <path> - read release notes from a file instead.
• -notary-profile <name> - notarytool keychain profile (default kaze-notary).
• -homebrew - also publish/update Casks/kaze.rb in fayazara/homebrew-tap. Off by default because the tap has no Kaze cask yet; only pass it when the user wants Kaze on Homebrew.
• -yes / -y - assume "yes" for all confirmation prompts (non-interactive).

Triggering a full release from here (recommended)

1. Decide the version and build number. The build number (CURRENT_PROJECT_VERSION) must increase every release or Sparkle won't offer the update. Check the current values:

   grep -E "MARKETING_VERSION|CURRENT_PROJECT_VERSION" \
     Kaze.xcodeproj/project.pbxproj | sort -u

   Pick the next MARKETING_VERSION (dotted semver, never regress) and CURRENT_PROJECT_VERSION = current + 1.
2. Make sure code changes are committed and pushed to main first, so the release tag points at the released source. (The CLI commits the version bump and pushes the appcast, but it does not push your other unrelated commits.)
3. Run it (non-interactive, safe to run from a tool call):

   cd /Users/fayazahmed/Developer/fayazara/mac/Kaze && \
   go run ./cmd/kaze-release -build -yes \
     -set-version <x.y.z> -set-build <n> \
     -notes "First note
   Second note"

   Notarization blocks for a few minutes - this is expected, not a hang. Use a generous tool timeout (~10 min; the archive also compiles MLX).

Package-only (app already exported by the user)

cd /Users/fayazahmed/Developer/fayazara/mac/Kaze && \
go run ./cmd/kaze-release -yes -notes "Your notes here"