mahout-release

Coordinate the Apache Mahout release process with gated approvals and artifact publication.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/guan404ming/gmccc --skill mahout-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mahout-release
Source: https://github.com/guan404ming/gmccc/tree/main/skills/mahout/mahout-release
Command: npx skills add https://github.com/guan404ming/gmccc --skill mahout-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and guide the Apache Mahout release process to ensure consistent, auditable artifacts.

Core Features & Use Cases

  • RC preparation and branch management
  • Version updates across pyproject.toml and qdp/Cargo.toml
  • Multi-architecture builds and artifact signing (GPG) and hashing
  • Uploads to TestPyPI and PyPI with verification steps
  • Release planning, issue generation, and stakeholder communication
  • Documentation tagging and final publication steps

Quick Start

Initiate the Mahout release workflow and execute each phase exactly as documented in dev/release.md.

Frequently Asked Questions about mahout-release

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

FAQPage Schema
How do I automate PyPI releases with maturin for a Rust and Python project?

To automate a PyPI release with maturin, you update versions in pyproject.toml and Cargo.toml, build multi-architecture artifacts, sign and hash them, and upload to TestPyPI and PyPI with gated approvals between phases.

What is the standard release workflow for coordinating multi-arch Python builds and GPG signing?

The standard release workflow for multi-arch Python builds involves RC preparation, version updates, building artifacts with maturin, GPG signing and hashing, and final publication with stakeholder communication and documentation tagging.

Does the Mahout release process require updating both pyproject.toml and qdp/Cargo.toml versions?

Yes, the Mahout release process strictly requires updating version numbers in both pyproject.toml and qdp/Cargo.toml to ensure consistent, auditable artifacts before proceeding to multi-architecture builds and publication.

Can I upload to TestPyPI and PyPI with verification steps using a guided release workflow?

Yes, you can upload to TestPyPI and PyPI with verification steps by following a guided workflow that enforces artifact signing, hashing, and gated approvals between the TestPyPI verification and final PyPI publication phases.

What's the best way to manage RC preparation and branch management for a maturin build?

The best way to manage RC preparation for a maturin build is to follow a structured release process that coordinates branch management, version updates, and gated approvals to generate consistent, auditable release candidate artifacts.

Why does my Apache Mahout release workflow require gated approvals between phases?

Gated approvals are required in the Apache Mahout release workflow to enforce strict requirements like version updates and artifact signing, ensuring consistent, auditable artifacts before moving between RC preparation, TestPyPI, and PyPI publication.