release

Automate LogTape release workflows with version bumps, CHANGES.md updates, and git tags.

1.9k|46|Updated Apr 16, 2024
One-click install
npx skills add https://github.com/dahlia/logtape --skill release-dahlia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/dahlia/logtape/tree/main/.claude/skills/release
Command: npx skills add https://github.com/dahlia/logtape --skill release-dahlia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the release process for the LogTape project. It ensures version bumps, updates to CHANGES.md, tag creation, and branch management are performed consistently and safely across maintenance and main branches.

Core Features & Use Cases

  • Automates patch and major/minor releases with proper versioning and tag messages.
  • Updates CHANGES.md, creates git tags, and pushes changes across maintenance and main branches.
  • Supports cascade merges across maintenance branches and keeps unreleased sections synchronized.

Quick Start

Initiate a patch release by bumping the version, updating CHANGES.md, tagging, and pushing changes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git release tagging and changelog updates?

Automate git release tagging and changelog updates by coordinating end-to-end version bumping, CHANGES.md modifications, deterministic tag creation, and branch pushes across maintenance and main branches.

What is the process for managing patch releases across maintenance branches?

Managing patch releases across maintenance branches involves bumping the version, updating CHANGES.md, creating git tags, pushing changes, and performing cascade merges to keep unreleased sections synchronized.

How does branch management work during major and minor version releases?

Branch management during major and minor releases coordinates updates across maintenance and main branches, verifying remote naming, branch state, and test execution before applying deterministic git tags and pushes.

What checks are needed before creating a git tag for a release?

Checks needed before creating a git tag for a release include verifying remote naming, confirming branch state, running test execution, and ensuring deterministic tagging rules are met as described in the project specifications.

Can I synchronize unreleased changelog sections across different branches?

You can synchronize unreleased changelog sections by applying cascade merges across maintenance branches, ensuring CHANGES.md updates remain consistent throughout the versioning and release workflow.

Why does automated version bumping fail during branch maintenance?

Automated version bumping fails during branch maintenance when pre-release checks detect incorrect remote naming, unclean branch state, failed test execution, or non-compliant deterministic tagging conditions.