release

Bump project versions and generate the next changelog from pyproject.toml.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill release-hadenlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/release
Command: npx skills add https://github.com/hadenlabs/tasks --skill release-hadenlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a release bump (major/minor/patch) and generate the next changelog from the updated pyproject.toml version, reducing manual release toil.

Core Features & Use Cases

  • Automates version bumps (major, minor, patch) and pre-releases according to semver rules.
  • Updates pyproject.toml with the new version and generates the next-version changelog for release tagging.
  • Use Case: When preparing a new release, run the appropriate task (release:major, release:minor, release:patch, release:pre_release) to update versioning and changelog in one step.

Quick Start

Run the release task matching your desired bump (e.g., release:minor) to automatically update pyproject.toml and produce the next changelog.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Python version bumps and changelog generation in pyproject.toml?

Automating Python version bumps and changelog generation requires running a release task like release:major, release:minor, or release:patch to update the pyproject.toml version and create the next changelog for tagging in one step.

What's the best way to apply semantic versioning to a Python project using Taskfile?

Applying semantic versioning with Taskfile involves triggering release:major, release:minor, release:patch, or release:pre_release commands, which automatically apply semver rules to update project versioning and generate the changelog simultaneously.

Can I generate a pre-release changelog without manually editing pyproject.toml?

Generating a pre-release changelog without manual edits is possible by running the release:pre_release task, which automatically updates the pyproject.toml version and produces the next-version changelog for the pre-release tag.

Does this release automation tool work with projects that don't use pyproject.toml?

Release automation for projects not using pyproject.toml is not supported, as the tool specifically reads and updates the version field within pyproject.toml to trigger appropriate release tasks and generate the changelog.

How do I create a major release and update the changelog in one command?

Creating a major release and updating the changelog in one command is done by executing release:major, which bumps the major version in pyproject.toml and generates the next changelog reflecting the new version.

Why does my automated changelog show the wrong version after a release bump?

An automated changelog showing the wrong version after a release bump indicates the pyproject.toml version was not correctly updated before changelog generation, which the release tasks are designed to handle sequentially.