generate-sparkle-appcast

Generate Sparkle appcast.xml from notarized zips and publish bilingual release notes.

21.1k|669|Updated Jan 27, 2017
One-click install
npx skills add https://github.com/Caldis/Mos --skill generate-sparkle-appcast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-sparkle-appcast
Source: https://github.com/Caldis/Mos/tree/main/.codex/skills/generate-sparkle-appcast
Command: npx skills add https://github.com/Caldis/Mos --skill generate-sparkle-appcast

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python3, openssl, and includes scripts (resource) components.

What problem does it solve?

This skill automates the generation and publishing of Sparkle appcast.xml from the latest Mos build, including bilingual release notes, ensuring a smooth, auditable release workflow.

Core Features & Use Cases

  • Generate appcast.xml from a notarized build zip in build/ and publish to docs/ for hosting.
  • Create two hosted release notes pages (Chinese + English) and channel history pages for Sparkle to surface updates.
  • Ensure deduplication and non-regression by prepending the new release item to the appcast, while preserving existing items.

Quick Start

Run the Sparkle appcast generator script to produce appcast.xml from the latest Mos build and update release notes.

Frequently Asked Questions about generate-sparkle-appcast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Sparkle appcast.xml from a notarized build?

To generate Sparkle appcast.xml, run the generator script to process the notarized zip in your build directory, create the XML file, and automatically prepend the new release item while preserving existing appcast entries.

What is the best way to automate macOS release notes publishing for Sparkle?

Automating macOS release notes publishing involves generating bilingual release notes pages for zh and en locales, creating channel history pages for Sparkle to surface updates, and hosting them directly in the docs directory.

Do I need git and python3 to automate Sparkle appcast generation?

Yes, you need git, python3, and openssl installed to automate Sparkle appcast generation, as these dependencies are required to process notarized builds, sign appcasts, and manage repository publishing.

Does this appcast generator support beta and stable build channels?

Yes, this appcast generator supports beta and stable build channels, managing Sparkle channel history and generating corresponding release notes for both release workflows across zh and en locales.

How does the appcast update process avoid duplicating existing release items?

The appcast update process avoids duplicating existing release items by prepending the new release entry to the appcast.xml file, ensuring deduplication and non-regression while preserving all previously published update items.

Why does Sparkle appcast generation require openssl?

Sparkle appcast generation requires openssl to sign the appcast.xml file, ensuring that the generated update feed is cryptographically verified and secure for macOS applications to download and install updates.

Related Skills