magpie-release-verify-rc

Verify Apache release candidate artefacts, GPG signatures, checksums, and license headers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gpg, sha256sum, sha512sum, apache-rat, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the pre-flight verification of release candidates for Apache projects, ensuring artefact integrity, license headers, and version consistency before the voting process begins.

Core Features & Use Cases

  • Artefact Integrity: Checks GPG signatures and checksums for all release artefacts.
  • License Headers: Validates Apache RAT licence headers for compliance.
  • Version Consistency: Ensures version strings match across all manifest files.
  • Use Case: Before a release vote, this Skill can be used to verify the integrity of the release candidate, ensuring it meets all necessary criteria.

Quick Start

Verify the release candidate for version 2.11.0-rc1 using the magpie-release-verify-rc skill.

Frequently Asked Questions about magpie-release-verify-rc

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

FAQPage Schema
How do I automate release candidate verification for Apache projects?

Automate release candidate verification by validating GPG signatures, SHA checksums, Apache RAT license headers, and version consistency across manifest files before the voting process begins.

What is checked during Apache release candidate integrity verification?

Release candidate integrity verification checks GPG signatures for artefacts, validates SHA256 and SHA512 checksums, ensures Apache RAT license header compliance, and confirms version strings match across manifests.

Do I need GPG and apache-rat installed to verify Apache release artefacts?

Yes, verifying Apache release artefacts requires GPG for signature verification, SHA256 and SHA512 checksums for integrity, and apache-rat to validate license headers across the project files.

What's the best way to ensure version consistency in Apache release management?

Ensure version consistency by automating checks that compare version strings across all manifest files, confirming they match before the release candidate enters the Apache voting process.

When should I run license header checks for Apache release candidates?

Run license header checks using apache-rat before the release vote begins to validate compliance, ensuring all artefacts meet Apache Software Foundation release management criteria.