magpie-release-rc-cut

Automates ASF release candidate creation with gpg signing, checksums, and staging.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-release-rc-cut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-release-rc-cut
Source: https://github.com/apache/magpie/tree/main/skills/release-rc-cut
Command: npx skills add https://github.com/apache/magpie --skill magpie-release-rc-cut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of cutting release candidates (RCs) for ASF projects, from tagging the release, building artifacts, signing each artifact, generating checksums, to staging them to the adopter's distribution backend. It minimizes local interaction to enhance security and ensure compliance with ASF protocols.

Core Features & Use Cases

  • Automated Release Candidate Creation: Automates the generation of RC tags and the creation of artifact lists.
  • Secure Signatures: Utilizes gpg for secure detachment and signing of artifacts.
  • Checksum Generation: Computes checksums (SHA-512 by default, SHA-256 if configured) for artifact integrity verification.
  • Staging Commands: Issues commands to stage artifacts to the adopter's distribution backend according to the backend configuration.
  • Use Case: Ideal for Release Managers who need to streamline the RC process, ensuring that release candidates are properly prepared and staged without exposing sensitive credentials or handling the signing key locally.

Quick Start

Cut an RC for '2.11.0' with version 'rc1' using the 'release-rc-cut' skill.

Frequently Asked Questions about magpie-release-rc-cut

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

FAQPage Schema
How do I automate Apache release candidate creation and artifact signing?

Apache release candidate creation is automated by managing tags, builds, artifact signing with gpg, checksum generation, and staging to a distribution backend. This minimizes local interaction to enhance security and ensure compliance with ASF protocols.

What checksums are generated during the release candidate staging process?

Checksums for artifact integrity verification are generated during the release candidate staging process, computing SHA-512 by default and SHA-256 if specifically configured in your release setup.

Can I use gpg to sign release artifacts without exposing my signing key locally?

You can sign release artifacts with gpg without exposing your signing key locally, as this skill minimizes local interaction to securely detach and sign artifacts during the release candidate cut.

What is the best way to cut a release candidate for an ASF project?

The best way to cut a release candidate for an ASF project is to automate tagging, building, signing, checksum generation, and staging, ensuring release candidates are properly prepared without handling sensitive credentials locally.

Does release candidate staging require access to a specific distribution backend configuration?

Release candidate staging requires access to release configuration and backend staging capabilities, issuing commands to stage artifacts to the adopter's distribution backend according to the backend configuration.