release

Bump version, build artifacts, and publish galaxy-mcp to PyPI.

37|23|Updated Mar 25, 2025

Search Tags:#automation #git #workflow #versioning #release #github-actions #pyPI

Ready to run

npx skills add https://github.com/galaxyproject/galaxy-mcp --skill release-galaxyproject

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Release management for galaxy-mcp is complex and risky: it requires accurate version bumps, careful gating, and coordination between Git, CI, and PyPI to avoid irreversible deployments. This Skill orchestrates the end-to-end release workflow, ensuring governance and reproducibility.

## Core Features & Use Cases

End-to-end release orchestration: bump version, build, publish to PyPI with verification.
Phase-gated workflow: phase 0 preconditions, phase 1 notes, phase 2 pre-publish checks.
Post-release dev bump: revert to next dev version.
Release notes curation: manage draft tags and notes.
Safety: ensures irreversible PyPI publish is only done with explicit approval.

### Quick Start Trigger the release workflow to bump the version, build artifacts, and publish galaxy-mcp to PyPI.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate publishing a Python package to PyPI using GitHub Actions?▼

Automating a PyPI release through GitHub Actions requires orchestrating version bumps, artifact building, and secure publishing. This release workflow manages the end-to-end process, enforcing gating and explicit approval before deploying to PyPI.

What is a phase-gated release workflow for version control?▼

A phase-gated release workflow enforces sequential approval steps before deployment. It applies preconditions, release notes generation, and pre-publish checks across distinct phases to ensure version bumps and irreversible PyPI deployments are fully verified.

How do I safely bump versions and generate release notes for a Python project?▼

Safely bumping versions requires inferring the next version from the main branch and verifying lockfile integrity. This release process curates draft tags, generates release notes, and ensures versioning is applied before building artifacts.

Can I enforce explicit approval before an irreversible PyPI publish?▼

Enforcing explicit approval before PyPI deployment prevents irreversible publishing mistakes. This release workflow applies phase-gated safety checks, requiring manual confirmation before tagging releases and publishing to PyPI.

Do I need uv.lock integrity verification before building Python artifacts?▼

Verifying uv.lock integrity is required to ensure dependency reproducibility before building artifacts. The release workflow enforces this precondition during phase 0 to guarantee that the environment matches the expected state before versioning.

Why does my automated GitHub Actions release fail to revert to a dev version?▼

Reverting to a dev version is a post-release step to ensure the repository is ready for the next development cycle. This release workflow automates the dev bump immediately after successfully publishing to PyPI and tagging the release.