releasing-desktop

Automate desktop release workflows for macOS and Windows with version bump, builds, signing, and git tagging.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fran0220/jacoworks --skill releasing-desktop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-desktop
Source: https://github.com/fran0220/jacoworks/tree/main/.agents/skills/releasing-desktop
Command: npx skills add https://github.com/fran0220/jacoworks --skill releasing-desktop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end release workflow management for JAcoworks Desktop, ensuring version bumps, multi-platform builds, signing/notarization, and deployment are repeatable and auditable.

Core Features & Use Cases

  • End-to-end desktop release workflow covering macOS (arm64/x86_64) and Windows (x64)
  • Automatic version bump, build, sign, notarize, and upload to COS
  • Register release in database and create git tag for traceability
  • Use Case: When you need to release a new desktop version after code freeze, this skill executes all necessary steps with minimal manual intervention.

Quick Start

Run a full release for a new version by bumping the version field and executing the release workflow.

Frequently Asked Questions about releasing-desktop

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

FAQPage Schema
How do I automate Tauri desktop releases for macOS and Windows?

Automating Tauri desktop releases end-to-end handles version bump, multi-platform builds, signing, and COS upload in a single workflow. It executes all necessary steps with minimal manual intervention after code freeze.

What is the best way to manage desktop app signing and notarization?

Managing desktop app signing and notarization requires applying platform-specific cryptographic signatures to build artifacts before deployment. The workflow automatically signs and notarizes builds for macOS arm64/x86_64 and Windows x64 platforms.

How do I upload desktop release artifacts to COS and register them in a database?

Uploading desktop release artifacts to COS and registering them involves transferring build outputs to remote storage and recording metadata. The workflow uploads signed artifacts to COS, registers the release in a database, and creates a git tag.

Does this release workflow support both macOS arm64 and Windows x64 builds?

Yes, this release workflow supports multi-platform desktop releases covering macOS arm64/x86_64 and Windows x64. It applies platform-specific builds, signing, notarization, and COS upload configurations for each target architecture.

How does git tagging ensure traceable deployment for desktop releases?

Git tagging ensures traceable deployment by creating a specific repository marker linked to the released version. The workflow creates git tags after successful builds and COS uploads, providing an auditable record of the exact code state deployed.