vesper-release-distribution

Automate Vesper desktop release workflows with version validation and artifact verification.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-release-distribution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vesper-release-distribution
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/vesper-release-distribution
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-release-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, node, gh, git, and includes scripts (resource) components.

What problem does it solve?

This skill streamlines Vesper desktop release operations by automating version validation, artifact checks, and publishing/mirroring to internal releases, reducing manual toil and errors.

Core Features & Use Cases

  • Validate release readiness by inspecting apps/electron/package.json and shared version markers, ensuring alignment with the repo's release policy.
  • Publish and mirror releases across external and internal targets, including sipherxyz/vesper-internal-release, with prechecks and artifact verification.
  • Diagnose and rerun failed releases by inspecting workflow gates (.github/workflows/desktop.yml and .github/workflows/publish-internal-release.yml) and release metadata.

Quick Start

Bump the version and run the release workflow, then monitor prechecks, builds, and the internal mirror.

Frequently Asked Questions about vesper-release-distribution

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

FAQPage Schema
How do I automate desktop app release workflows with GitHub?

Automate desktop app release workflows by validating version bumps in package.json, gating publish steps, and ensuring internal mirrors through GitHub workflow scripts.

What is the best way to validate version bumps before publishing a desktop release?

Validate version bumps by tracing version sources from apps/electron/package.json and shared app-version.ts, ensuring alignment with the repository's release policy.

Do I need Bun and Node installed to run release automation scripts?

Yes, you need Bun, Node, gh, and git installed as dependencies to execute the release automation scripts and interact with GitHub workflows.

How does internal release mirroring work for GitHub repositories?

Internal release mirroring synchronizes release artifacts and metadata to internal targets like sipherxyz/vesper-internal-release after prechecks and artifact verification pass.

Why does my GitHub desktop release workflow fail during prechecks?

Desktop release workflows fail during prechecks when version markers in package.json and app-version.ts mismatch or when workflow gates in desktop.yml reject unverified artifacts.

Can I diagnose failed GitHub releases by inspecting workflow files?

Yes, you can diagnose failed releases by inspecting workflow gates in .github/workflows/desktop.yml and publish-internal-release.yml alongside generated release metadata.