From fd1375e2ad40fbf278f75d796b01a74b5762f404 Mon Sep 17 00:00:00 2001 From: Thomas Ricouard Date: Wed, 7 Jan 2026 12:38:14 +0100 Subject: [PATCH] Add instructions for tagging and GitHub releases Updated SKILL.md and release.md to include steps for creating a git tag and publishing a GitHub release with the app zip and appcast. This provides clearer guidance for distributing releases via GitHub. --- macos-spm-app-packaging/SKILL.md | 1 + macos-spm-app-packaging/references/release.md | 17 +++++++++++++++++ 2 files changed, 18 insertions(+) diff --git a/macos-spm-app-packaging/SKILL.md b/macos-spm-app-packaging/SKILL.md index be3c0f1..5506dc6 100644 --- a/macos-spm-app-packaging/SKILL.md +++ b/macos-spm-app-packaging/SKILL.md @@ -20,6 +20,7 @@ Bootstrap a complete SwiftPM macOS app folder, then build, package, and run it w - Package: `Scripts/package_app.sh`. - Run: `Scripts/compile_and_run.sh` (preferred) or `Scripts/launch.sh`. - Release (optional): `Scripts/sign-and-notarize.sh` and `Scripts/make_appcast.sh`. + - Tag + GitHub release (optional): create a git tag, upload the zip/appcast to the GitHub release, and publish. ## Templates - `assets/templates/package_app.sh`: Build binaries, create the .app bundle, copy resources, sign. diff --git a/macos-spm-app-packaging/references/release.md b/macos-spm-app-packaging/references/release.md index cbcd127..a95a097 100644 --- a/macos-spm-app-packaging/references/release.md +++ b/macos-spm-app-packaging/references/release.md @@ -12,3 +12,20 @@ - Install Sparkle tools so `generate_appcast` is on PATH. - Provide `SPARKLE_PRIVATE_KEY_FILE` (ed25519 key). - The appcast script uses your zip artifact to create an updated `appcast.xml`. + +## Tag and GitHub release (optional) +Use a versioned git tag and publish a GitHub release with the notarized zip (and appcast if you host it on GitHub Releases). + +Example flow: +``` +git tag v +git push origin v + +gh release create v CodexBar-.zip appcast.xml \ + --title "AppName " \ + --notes-file CHANGELOG.md +``` + +Notes: +- If you serve appcast from GitHub Releases or raw URLs, ensure the release is published and assets are accessible (no 404s). +- Prefer using a curated release notes file rather than dumping the full changelog.