release-pypi

Name: release-pypi
Availability: InStock
Author: Podonos

Automate Python SDK releases from version bumping to PyPI publishing.

8|2|Updated Apr 9, 2024

Search Tags:#automation #versioning #python #packaging #release #pypi #ci-cd

Ready to run

npx skills add https://github.com/podonos/podonos-pysdk --skill release-pypi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-pypi
Source: https://github.com/podonos/podonos-pysdk/tree/main/.claude/skills/release-pypi
Command: npx skills add https://github.com/podonos/podonos-pysdk --skill release-pypi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a Python SDK to PyPI involves many manual steps, from version bumps to publishing artifacts and creating releases. This skill automates the entire end-to-end PyPI release process to reduce human error and save time.

Core Features & Use Cases

Version bumping, validation, and synchronization between pyproject.toml and podonos/init.py to ensure a consistent release.
Pre-flight checks, building artifacts, uploading to Test PyPI, then production PyPI, with automated verification steps.
Git tagging, GitHub Release creation, and an optional release-branch workflow to align with team governance.

Quick Start

Trigger the release workflow by specifying a target version or bump type (patch, minor, major, or an explicit version) to begin the end-to-end release process.

Frequently Asked Questions about release-pypi

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

FAQPage Schema

How do I automate the Python PyPI release workflow end to end?▼

Automate the Python PyPI release workflow by bumping versions, running tests, building artifacts, uploading to Test PyPI and production PyPI, and creating GitHub releases with minimal manual intervention.

How does version bumping work when releasing a Python package to PyPI?▼

Version bumping for a Python package release synchronizes the version number between pyproject.toml and package initialization files, supporting patch, minor, major, or explicit version targets to ensure a consistent release.

What steps are required to publish a Python SDK to Test PyPI before production?▼

Publishing to Test PyPI before production requires pre-flight checks, local install sanity verification, building artifacts, uploading to Test PyPI, and running automated post-upload verification steps.

Can I create GitHub releases and Git tags automatically as part of a Python packaging release?▼

Yes, you can create GitHub releases and Git tags automatically as part of a Python packaging release, with an optional release-branch workflow to align with team governance and reduce manual intervention.

Do I need a user confirmation gate before uploading Python artifacts to production PyPI?▼

Yes, a user confirmation gate is included before uploading verified Python artifacts to production PyPI, ensuring a human approves the release after test verification and before the final publish step.

What is the best way to verify a Python package release after publishing to PyPI?▼

The best way to verify a Python package release after publishing to PyPI is through automated post-release verification, which checks the uploaded artifacts and confirms the package is installable and functional.