plainx-release

Bump versions, generate changelogs, and tag Git releases for Python packages.

1.0k|27|Updated Mar 22, 2023
One-click install
npx skills add https://github.com/dropseed/plain --skill plainx-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plainx-release
Source: https://github.com/dropseed/plain/tree/main/plainx-dev/plainx/dev/agents/.claude/skills/plainx-release
Command: npx skills add https://github.com/dropseed/plain --skill plainx-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releases plainx packages by bumping versions, generating changelogs, and tagging Git releases, enabling predictable, automated distribution.

Core Features & Use Cases

  • Automated versioning aligned with commit history and user-specified release type (major/minor/patch)
  • Changelog generation and tagging ready for PyPI publication
  • Optional GitHub Actions workflow setup to publish on tag pushes

Quick Start

Run the release workflow to bump the next version, generate a changelog, and create a Git tag.

Frequently Asked Questions about plainx-release

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

FAQPage Schema
How do I automate Python package versioning and changelog generation for a release?

Automate Python package versioning by analyzing commit history to bump versions, generating changelogs, and tagging Git releases for predictable distribution. It guides you through committing, tagging, and pushing changes.

Can I use this release workflow for a Python monorepo?

Yes, you can use this release workflow for Python monorepos. It supports both single-package and monorepo projects when preparing or publishing a new version based on commit history.

How do I publish a new package version to PyPI using Git tags?

Publish a new package version to PyPI by bumping the version, generating release notes, and optionally configuring a GitHub Actions workflow to automatically publish on tag pushes.

How are major, minor, and patch versions selected during an automated release?

Major, minor, and patch versions are selected based on your commit history. The workflow implements pre-release checks and prompts you to specify the release type before generating release notes and tagging.

What's the best way to set up a GitHub Actions workflow to publish Python packages on tag pushes?

Set up a GitHub Actions workflow to publish Python packages by optionally configuring it during the release process. It triggers publication automatically when new Git release tags are pushed.

Does automated Python versioning require a pyproject.toml file?

Automated Python versioning applies to projects using pyproject.toml. The workflow uses this configuration to bump versions, generate changelogs, and prepare the package for PyPI publication.