원클릭으로 Manus에서 모든 스킬 실행

sparkle-github-release

스타0

포크0

업데이트2026년 3월 13일 04:13

Set up and manage macOS app releases with Sparkle auto-update via GitHub Actions. Use when the user needs to (1) configure the macOS release pipeline (build, sign, notarize, distribute), (2) integrate Sparkle framework for auto-updates in a Swift macOS app, (3) create or modify the GitHub Actions release workflow (macos-release.yml), (4) generate or debug Sparkle appcast.xml feeds, (5) configure or rotate signing/notarization secrets, (6) set up GitHub Pages deployment for appcast hosting, (7) write or update CI scripts for code signing, notarization, or appcast generation, or (8) troubleshoot DMG creation, notarization failures, or Sparkle update issues.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

rxtech-lab

rxtech-lab/agent-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Sparkle GitHub Release

macOS app release pipeline: GitHub Actions for building, code signing, notarization, and Sparkle auto-update distribution.

Architecture

GitHub Release (vX.Y.Z tag)
         │
         ▼
  GitHub Actions (self-hosted macOS)
         │
         ├──► xcodebuild archive (manual signing, hardened runtime)
         │
         ├──► Sign Sparkle framework artifacts
         │
         ├──► Create DMG + notarize with Apple
         │
         ├──► Generate appcast.xml (EdDSA signatures)
         │
         ├──► Upload DMG to GitHub Release
         │
         ▼
  GitHub Actions (ubuntu-latest)
         │
         └──► Deploy appcast.xml + release notes to GitHub Pages
                    │
                    ▼
           update.{domain}/appcast.xml ◄── Sparkle checks for updates

Release Workflow

Creating a release

Ensure all GitHub secrets are configured → See secrets.md
Create a GitHub Release with a semver tag (e.g. v1.0.0)
Write release notes in the release body (Markdown)
The workflow automatically builds, signs, notarizes, and deploys
The DMG appears as a release asset; appcast.xml is deployed to Pages
Users with the app installed receive the update via Sparkle

Pipeline stages

Stage	Tool	Output
Archive	`xcodebuild archive`	`.xcarchive` with hardened runtime
Sign Sparkle	`sign-sparkle.sh`	Re-signed Sparkle XPC services + framework
DMG + Notarize	`notary.sh` + `create-dmg`	Notarized, stapled `.dmg`
Appcast	`generate-appcast.sh`	`appcast.xml` with EdDSA signatures
Deploy	GitHub Pages action	`update.{domain}/appcast.xml`

Version identifiers

Field	Build Setting	Source	Example
Version	`MARKETING_VERSION`	Release tag (e.g. `1.0.0`)	`1.2.3`
Build	`CURRENT_PROJECT_VERSION`	GitHub Actions run number	`42`

File Reference

File	Purpose
`.github/workflows/macos-release.yml`	Full release pipeline (build + deploy)
`scripts/ci-set-manual-signing.sh`	Switch to manual code signing for CI
`scripts/update-version.sh`	Stamp version numbers from release tag
`scripts/sign-sparkle.sh`	Re-sign Sparkle framework for notarization
`scripts/notary.sh`	Create DMG and notarize with Apple
`scripts/generate-appcast.sh`	Generate Sparkle appcast.xml feed
`scripts/convert-markdown.py`	Convert release notes to styled HTML
`scripts/update-xml.py`	Patch appcast.xml with release notes links
`bin/generate_appcast`	Sparkle binary for appcast generation

Scripts

Script	Args	Purpose
`ci-set-manual-signing.sh`	`<identity> <profile_name>`	Patch project.pbxproj for manual signing
`update-version.sh`	`<version> [build_number]`	Update MARKETING_VERSION and build number
`sign-sparkle.sh`	(none, uses env)	Re-sign Sparkle binaries with hardened runtime
`notary.sh`	(none, uses env)	Create DMG, notarize, and staple
`generate-appcast.sh`	(none, uses env)	Generate appcast.xml with EdDSA signatures
`convert-markdown.py`	`<input.md> <output.html>`	Markdown to styled HTML for release notes
`update-xml.py`	`<appcast.xml> <notes_path> [build_number]`	Add release notes link and build number to appcast

Read references/scripts.md for detailed script documentation including environment variables and implementation details.

References

GitHub Actions workflow (trigger, jobs, archive command, deploy): github-actions.md
Sparkle integration (Swift setup, Info.plist, SPM dependency): sparkle-integration.md
Scripts (all CI scripts with env vars and behavior): scripts.md
Secrets management (required secrets, how to generate each one): secrets.md

이 저장소의 다른 Skills

같은 저장소

react-native-android-release

rxtech-lab/agent-skills

Set up and manage React Native (Expo/EAS) Android releases via GitHub Actions. Use when the user needs to (1) configure the Android release pipeline (local EAS build, version bump, Google Play submit), (2) create or modify the GitHub Actions release workflow (android-release.yml), (3) set up or debug eas.json build/submit profiles, (4) configure the Google Play service-account credential as a base64 secret, (5) wire EXPO_TOKEN and EAS-managed signing keystore, (6) bump app.json version from a release tag with EAS remote versionCode auto-increment, (7) publish an AAB to the Google Play internal track via EAS Submit, or (8) fall back to a bare React Native Gradle + Fastlane path when not using Expo managed workflow.

2026-06-020

macos-extensionkit

rxtech-lab/agent-skills

Build a macOS app that hosts its own in-app UI extension using Apple's ExtensionKit / ExtensionFoundation (AppExtension, AppExtensionPoint, EXHostViewController, NSXPC). Use when creating a host app + bundled app-extension target, defining a custom extension point, sharing an API/XPC contract core between host and extension, embedding extension SwiftUI inside the host, wiring bidirectional host↔extension messaging, or debugging extension discovery/activation failures (OSStatus -10814, "Failed to get extension process and XPC endpoints", LSRegisterURL -10819).

2026-06-020

argo-trading

rxtech-lab/agent-skills

Iterate on algorithmic trading strategies in ArgoTradingSwift (`.rxtrading` documents) via the embedded MCP server. Use when the user wants to write, build, backtest, or improve Go-based trading strategies that compile to WASM, load a `.wasm` strategy into the app, run a backtest against a schema/dataset, or analyze backtest results (stats.yaml + per-trade parquet). Triggers include phrases like "write a trading strategy", "backtest this strategy", "beat buy-and-hold", "load_strategy", "run_backtest", and any mention of argo-trading, ArgoTradingSwift, or `.rxtrading` files.

2026-04-190

ios-auto-release

rxtech-lab/agent-skills

Manage the two-stage iOS release pipeline using GitHub Actions for CI/semantic versioning and Xcode Cloud for App Store distribution. Use when the user needs to (1) trigger a new iOS release, (2) understand or modify CI workflows (ios-ci.yml, ios-setup.yml, create-release.yaml), (3) debug version bumping or Xcode Cloud builds, (4) update the ci_post_clone.sh script, (5) configure or rotate CI secrets, (6) understand conventional commit conventions for version bumps, or (7) troubleshoot failed releases or TestFlight submissions.

2026-02-240

openapi-integration

rxtech-lab/agent-skills

Set up and maintain OpenAPI 3.0 integration between a Next.js backend and a Swift iOS client. Use when the user needs to (1) set up OpenAPI spec generation from Zod schemas using next-openapi-gen, (2) configure Swift OpenAPI generator for an iOS package, (3) create or update API routes with JSDoc annotations, (4) create Zod schemas for API contracts, (5) sync the OpenAPI spec between backend and iOS, (6) create Swift service layers wrapping generated API clients, or (7) troubleshoot OpenAPI generation or Swift type issues.

2026-02-070

skill-creator

rxtech-lab/agent-skills

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-02-070

name

sparkle-github-release

description

Sparkle GitHub Release

macOS app release pipeline: GitHub Actions for building, code signing, notarization, and Sparkle auto-update distribution.

Architecture

GitHub Release (vX.Y.Z tag)
         │
         ▼
  GitHub Actions (self-hosted macOS)
         │
         ├──► xcodebuild archive (manual signing, hardened runtime)
         │
         ├──► Sign Sparkle framework artifacts
         │
         ├──► Create DMG + notarize with Apple
         │
         ├──► Generate appcast.xml (EdDSA signatures)
         │
         ├──► Upload DMG to GitHub Release
         │
         ▼
  GitHub Actions (ubuntu-latest)
         │
         └──► Deploy appcast.xml + release notes to GitHub Pages
                    │
                    ▼
           update.{domain}/appcast.xml ◄── Sparkle checks for updates

Release Workflow

Creating a release

Ensure all GitHub secrets are configured → See secrets.md
Create a GitHub Release with a semver tag (e.g. v1.0.0)
Write release notes in the release body (Markdown)
The workflow automatically builds, signs, notarizes, and deploys
The DMG appears as a release asset; appcast.xml is deployed to Pages
Users with the app installed receive the update via Sparkle

Pipeline stages

Stage	Tool	Output
Archive	`xcodebuild archive`	`.xcarchive` with hardened runtime
Sign Sparkle	`sign-sparkle.sh`	Re-signed Sparkle XPC services + framework
DMG + Notarize	`notary.sh` + `create-dmg`	Notarized, stapled `.dmg`
Appcast	`generate-appcast.sh`	`appcast.xml` with EdDSA signatures
Deploy	GitHub Pages action	`update.{domain}/appcast.xml`

Version identifiers

Field	Build Setting	Source	Example
Version	`MARKETING_VERSION`	Release tag (e.g. `1.0.0`)	`1.2.3`
Build	`CURRENT_PROJECT_VERSION`	GitHub Actions run number	`42`

File Reference

File	Purpose
`.github/workflows/macos-release.yml`	Full release pipeline (build + deploy)
`scripts/ci-set-manual-signing.sh`	Switch to manual code signing for CI
`scripts/update-version.sh`	Stamp version numbers from release tag
`scripts/sign-sparkle.sh`	Re-sign Sparkle framework for notarization
`scripts/notary.sh`	Create DMG and notarize with Apple
`scripts/generate-appcast.sh`	Generate Sparkle appcast.xml feed
`scripts/convert-markdown.py`	Convert release notes to styled HTML
`scripts/update-xml.py`	Patch appcast.xml with release notes links
`bin/generate_appcast`	Sparkle binary for appcast generation

Scripts

Script	Args	Purpose
`ci-set-manual-signing.sh`	`<identity> <profile_name>`	Patch project.pbxproj for manual signing
`update-version.sh`	`<version> [build_number]`	Update MARKETING_VERSION and build number
`sign-sparkle.sh`	(none, uses env)	Re-sign Sparkle binaries with hardened runtime
`notary.sh`	(none, uses env)	Create DMG, notarize, and staple
`generate-appcast.sh`	(none, uses env)	Generate appcast.xml with EdDSA signatures
`convert-markdown.py`	`<input.md> <output.html>`	Markdown to styled HTML for release notes
`update-xml.py`	`<appcast.xml> <notes_path> [build_number]`	Add release notes link and build number to appcast

Read references/scripts.md for detailed script documentation including environment variables and implementation details.

References

GitHub Actions workflow (trigger, jobs, archive command, deploy): github-actions.md
Sparkle integration (Swift setup, Info.plist, SPM dependency): sparkle-integration.md
Scripts (all CI scripts with env vars and behavior): scripts.md
Secrets management (required secrets, how to generate each one): secrets.md