release-mac

Automate Spark macOS DMG publication to GitHub Releases with version-aligned git tagging.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/automatedigital/spark --skill release-mac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-mac
Source: https://github.com/automatedigital/spark/tree/main/.agents/skills/release-mac
Command: npx skills add https://github.com/automatedigital/spark --skill release-mac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually publishing macOS desktop application builds to GitHub Releases requires juggling disjoint steps including version lookup, git tagging, asset uploading, and writing consistent release notes, which is time-consuming and prone to human error like mismatched version tags or missing end-user install instructions.

Core Features & Use Cases

  • Automated Version Detection: Pulls the app version directly from the Tauri configuration file to eliminate manual version lookup errors.
  • Safe Release Workflow: Enforces user confirmation before creating git tags or publishing releases, and warns about uncommitted changes to prevent accidental releases of unstable builds.
  • Flexible Release Handling: Supports both creating new GitHub Releases with pre-formatted install notes and uploading assets to existing releases for patch updates.
  • Use Case: Spark desktop developers can use this skill to publish a new macOS DMG build in under a minute, with all required git tags, release assets, and user-facing install instructions automatically generated, removing the need to run manual gh CLI commands or copy-paste release notes.

Quick Start

Use the release-mac skill to publish the latest Spark.dmg build to a new GitHub Release with the correct desktop version tag and pre-filled install instructions for macOS users.

Frequently Asked Questions about release-mac

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

FAQPage Schema
How do I automate publishing a macOS DMG to GitHub Releases?

To publish a macOS DMG, the workflow auto-detects the version from your Tauri configuration file, applies git tagging, uploads the DMG asset, and generates standardized install notes for macOS users.

How does version detection work for Tauri app release automation?

Release automation pulls the app version directly from the Tauri configuration file to eliminate manual lookup errors and ensure git tags match the desktop build.

Can I upload a DMG to an existing GitHub Release instead of creating a new one?

Yes, the release workflow supports uploading DMG assets to existing GitHub Releases for patch updates, as well as creating entirely new releases with pre-formatted install notes.

Does the macOS release workflow warn about uncommitted git changes?

Yes, the release workflow enforces safe publication by warning about uncommitted git changes and requiring user confirmation before creating git tags or publishing to prevent accidental unstable builds.

What are the limitations of automating macOS desktop release publication?

A limitation of this release automation is the enforced user confirmation before destructive git tagging actions, meaning it cannot run fully autonomously in non-interactive CI pipelines without manual approval.