release

Automate the Vorta release process from version bump to macOS builds.

2.5k|227|Updated Oct 27, 2018
One-click install
npx skills add https://github.com/borgbase/vorta --skill release-borgbase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/borgbase/vorta/tree/main/.claude/skills/release
Command: npx skills add https://github.com/borgbase/vorta --skill release-borgbase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vorta maintainers often juggle many steps to release a new version. This skill guides through the complete release process, reducing manual errors during version bumps, translations, git tagging, and macOS builds.

Core Features & Use Cases

  • End-to-end release workflow covering pre-checks, version bumps, translation updates, appdata changes, commits, and Git tags.
  • Orchestrates push to upstream, CI wait, changelog generation, GitHub release creation, PyPi publishing, and macOS builds.
  • Use Case: A maintainer releases a new version by following the guided steps with guardrails before destructive actions.

Quick Start

Run the release workflow by issuing /release to start the guided process.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a git release workflow from version bump to changelog generation?▼

End-to-end release workflow automation handles version bumps, git tags, CI checks, and changelog generation in a guided sequence. It coordinates the full release across Git, translations, packaging, and distribution platforms.

What's the best way to prevent destructive actions during a CI version-bump and release process?▼

Preventing destructive actions during a release process requires built-in guardrails that enforce pre-checks and prompt for human confirmation before critical steps like commits, tags, and pushes.

How does macOS build orchestration work within a GitHub release and PyPi publishing workflow?▼

macOS build orchestration within a release workflow waits for CI to pass, then automates appcast updates, GitHub release creation, PyPi publishing, and the final macOS builds sequentially.

Can I automate translation updates and appdata changes as part of an end-to-end release workflow?▼

End-to-end release workflows include translation updates and appdata changes alongside version bumps and git tags, ensuring all metadata and localization files are committed before pushing upstream.

Do I need human confirmation before pushing git tags and upstream commits in an automated release?▼

Human confirmation is required before pushing upstream commits and git tags in an automated release, as the workflow enforces guardrails to prevent destructive actions during critical steps.

Why does a release workflow require pre-checks before starting the version bump and tagging process?▼

A release workflow requires pre-checks before version bumping and tagging to verify repository readiness and prevent destructive actions, ensuring the maintainer coordinates the full release safely.