publish-desktop

Automate the Cline desktop release lifecycle with version synchronization and GitHub Actions.

65.9k|7.1k|Updated Jul 6, 2024
One-click install
npx skills add https://github.com/cline/cline --skill publish-desktop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-desktop
Source: https://github.com/cline/cline/tree/main/.cline/skills/publish-desktop
Command: npx skills add https://github.com/cline/cline --skill publish-desktop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the complex, multi-step process of releasing the Cline desktop application, ensuring version consistency, proper tagging, and secure deployment via GitHub Actions.

Core Features & Use Cases

  • Release Orchestration: Automates version bumping across package.json and tauri.conf.json files.
  • Workflow Management: Triggers and monitors the desktop-publish GitHub workflow, including notarization and signing.
  • Verification: Validates release notes, changelogs, and the auto-update feed to ensure a seamless experience for end users.

Quick Start

Use the publish-desktop skill to prepare and trigger the release process for the next version of the Cline desktop application.

Frequently Asked Questions about publish-desktop

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

FAQPage Schema
How do I automate desktop app releases using GitHub Actions and Tauri?

Automating desktop app releases with GitHub Actions and Tauri involves synchronizing version files, creating git tags, and triggering a deployment workflow. This process manages signed and notarized binaries while updating the auto-update feed for end users.

How does version synchronization work for Tauri desktop application deployments?

Version synchronization for Tauri deployments bumps version numbers across both package.json and tauri.conf.json files. This ensures version consistency before triggering the GitHub Actions workflow to tag and publish the release.

Do I need specific environment secrets to notarize macOS desktop binaries in GitHub Actions?

Notarizing macOS desktop binaries in GitHub Actions requires configuring PublishDesktop environment secrets. These secrets provide the necessary credentials for the workflow to sign and notarize the application binaries securely.

What is the best way to manage a rolling auto-update feed for a Tauri desktop application?

Managing a rolling auto-update feed for a Tauri desktop application requires validating release notes and changelogs after triggering the GitHub workflow. The automated deployment process maintains the feed to ensure seamless updates for end users.

How do I trigger the desktop-publish GitHub workflow for a new release?

Triggering the desktop-publish GitHub workflow requires coordinating repository version files and GitHub release tags. Once versions are synchronized and tagged, the workflow executes to build, sign, and deploy the application automatically.