release

Automate versioned software releases with changelogs and GitHub publishing.

23|4|Updated Sep 5, 2013

Search Tags:#automation #git #changelog #versioning #github #release

Ready to run

npx skills add https://github.com/drn/dots --skill release-drn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/drn/dots/tree/main/agents/skills/release
Command: npx skills add https://github.com/drn/dots --skill release-drn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire process of creating a new software release, from version bumping and changelog generation to tagging and publishing on GitHub.

Core Features & Use Cases

Automated Versioning: Automatically determines the next version number (major, minor, patch) or accepts a specific version.
Changelog Generation: Creates a categorized changelog based on Git commit history.
Tagging and Publishing: Creates a Git tag and publishes a GitHub release with the generated changelog.
Use Case: After merging a new feature, use this Skill to quickly create a patch release, update the version, generate the changelog, and push it to GitHub.

Quick Start

Use the release skill to create a patch release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate versioning and changelog generation from git history for a new release?▼

Automating versioning and changelog generation involves bumping versions based on commit history and creating categorized release notes. This skill processes Git commit history to automatically determine the next version and generate a categorized changelog for publishing.

Can I preview changelog generation and version bumps before publishing a GitHub release?▼

Yes, you can preview changelog generation and version bumps using the dry-run capability. This allows you to review the generated changes and verify the version increment before creating a Git tag or publishing to GitHub.

What is the best way to create a patch release using git and GitHub CLI?▼

Creating a patch release is best handled by automating version increments, generating changelogs, and tagging. This skill supports major, minor, and patch version increments, integrating with git and GitHub CLI to tag and publish releases directly.

Do I need to specify an explicit version number when creating a GitHub release?▼

No, you do not need to specify an explicit version number when creating a GitHub release. This skill supports automatic major, minor, and patch version bumps, but it also accepts an explicit version specification if you require a specific target version.

How does automated changelog generation categorize git commit history?▼

Automated changelog generation parses your git commit history to categorize changes for the new release. It extracts commit messages and organizes them into a structured changelog, which is then attached to the published GitHub release.

Are there limitations to using dry-run for previewing software release changes?▼

The dry-run capability allows you to preview version bumps and generated changelogs without making actual changes. It is limited to previewing; no Git tags are created and nothing is published to GitHub until you execute the release without the dry-run option.