release-oliphaunt

Coordinate Oliphaunt release preparation, publication, verification, and recovery across registries.

94|10|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/f0rr0/oliphaunt --skill release-oliphaunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-oliphaunt
Source: https://github.com/f0rr0/oliphaunt/tree/main/.codex/skills/release-oliphaunt
Command: npx skills add https://github.com/f0rr0/oliphaunt --skill release-oliphaunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents fragile, inconsistent Oliphaunt releases by coordinating exact-SHA qualification, multi-registry publication, release governance, and recovery across independently versioned products.

Core Features & Use Cases

  • Release Preparation and Auditing: Synchronize product versions, changelogs, semantic ownership, release plans, and qualification evidence.
  • Verified Publication: Freeze artifacts into an exhaustive publication lock, stage GitHub releases, publish registry packages, and verify public consumers across Cargo, npm, JSR, Maven Central, and SwiftPM.
  • Bootstrap and Recovery: Set up first-time registry identities, configure trusted publishers, resume partial releases, and perform tightly controlled same-version or pre-publication history repair.
  • Use Case: When an Oliphaunt release has qualified artifacts but a registry upload fails, use this Skill to inventory immutable state, validate the checkpoint chain, reconcile matching identities, and resume only the failed phase.

Quick Start

Use the release-oliphaunt skill to audit the current release state and prepare a verified release plan for the exact current commit.

Frequently Asked Questions about release-oliphaunt

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

FAQPage Schema
How do I publish verified GitHub releases across multiple registries like Cargo and npm?

Multi-registry publication freezes qualified artifacts into an exhaustive publication lock, stages GitHub releases, publishes packages across Cargo, npm, JSR, Maven Central, and SwiftPM, then verifies registry receipts and consumer resolution.

How do I resume a failed registry upload without restarting the entire release process?

Release recovery inventories immutable state, validates the checkpoint chain, reconciles matching identities, and resumes only the failed publication phase for the exact SHA.

What is exact-SHA artifact qualification for release automation?

Exact-SHA artifact qualification locks release artifacts to a specific commit hash, ensuring only verified builds tied to an immutable release transport are published.

Can I repair pre-publication history for a release that has already been partially staged?

Pre-publication history repair performs tightly controlled same-version fixes on staged releases, reconciling semantic ownership and release plans before any immutable publication occurs.

Does Release Please lifecycle management support independently versioned products in the same repository?

Release Please lifecycle management synchronizes product versions, changelogs, and semantic ownership across independently versioned products within a single coordinated release plan.

What is involved in first-identity bootstrap for trusted publishers on a new registry?

First-identity bootstrap sets up initial registry identities and configures trusted publishers, establishing the controlled Release Please lifecycle before any artifacts are published.