release

Automate version bumping, release notes, tests, Git tagging, and GitHub releases.

5|6|Updated Jul 5, 2022

Search Tags:#automation #devops #versioning #publishing #github #release

Ready to run

npx skills add https://github.com/ragnarok22/cryptobot_python --skill release-ragnarok22

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of preparing and publishing new software releases, ensuring consistency and saving valuable developer time.

Core Features & Use Cases

Version Management: Updates version numbers across project files (pyproject.toml, __init__.py).
Release Notes Generation: Facilitates the creation of release notes by prompting for user input and updating HISTORY.md.
Automated Testing: Ensures code quality by running tests before finalizing the release.
Git Tagging & GitHub Releases: Creates Git tags and publishes releases on GitHub for easy tracking and distribution.
Use Case: When you're ready to ship a new version of your Python package, this skill handles all the necessary steps from updating files to creating the GitHub release.

Quick Start

Use the release skill to prepare version 1.2.3 of the software.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Python package version bumping and GitHub release publishing?▼

Automating Python package version bumping and GitHub release publishing requires updating version numbers in pyproject.toml and __init__.py, compiling release notes in HISTORY.md, running tests, and creating Git tags via the GitHub CLI.

What steps are needed to prepare a new software release using Git and GitHub CLI?▼

To prepare a new software release using Git and GitHub CLI, you must validate semantic versioning, bump version numbers in project files, execute tests, generate Git tags, and publish the final GitHub release.

Does this release automation process require semantic versioning validation?▼

Yes, this release automation process requires strict semantic versioning validation to ensure correct version bumping across pyproject.toml and __init__.py before creating Git tags and GitHub releases.

Can I use GitHub CLI to streamline software release note compilation and Git tagging?▼

Yes, you can use GitHub CLI to streamline software release note compilation and Git tagging by prompting for user input to update HISTORY.md and subsequently pushing validated Git tags to GitHub.

What is the best way to manage automated testing before finalizing a Python package release?▼

The best way to manage automated testing before finalizing a Python package release is to execute test suites automatically after version bumping and before creating Git tags or publishing the GitHub release.

Why does automated version bumping update both pyproject.toml and __init__.py?▼

Automated version bumping updates both pyproject.toml and __init__.py to maintain version consistency across project configuration files and source code before publishing the GitHub release.