happier-release

Orchestrates exact-SHA releases and nightlies through preflight admission, immutable candidates, and verified publication.

1.6k|141|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/happier-dev/happier --skill happier-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: happier-release
Source: https://github.com/happier-dev/happier/tree/main/skills/happier-release
Command: npx skills add https://github.com/happier-dev/happier --skill happier-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Happier involves coordinating private release authority, CI evidence, immutable build candidates, and multi-channel promotion, and mistakes like rebuilding valid work or publishing from a dirty checkout cause failed or untrustworthy releases.

Core Features & Use Cases

  • Authority Resolution: Inspects the public release contract via node scripts/pipeline/run.mjs release-contract and bootstraps the private release authority with hmaint release bootstrap before any mutation.
  • Cheap Admission: Runs a non-mutating preflight that validates source identity, version projection, credentials, and runner prerequisites without repeating unit, typecheck, or E2E work from source CI.
  • Recovery & Verification: Routes failures through the happier-ci-stabilize recovery table (rerun, immutable-candidate resume, or fresh release) and closes only on terminal release status with promoted-reference evidence.
  • Use Case: A maintainer cutting a preview to main promotion uses this Skill to bind an exact-SHA CI run, resume a partially failed candidate build without rebuilding verified siblings, and advance issue stage labels only after post-promotion verification.

Quick Start

Ask the assistant to prepare and dispatch a Happier release for the current checkout, resolving the release authority and running preflight admission first.

Frequently Asked Questions about happier-release

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

FAQPage Schema
How do I run a Happier release from an exact commit SHA?

First inspect the public contract with `node scripts/pipeline/run.mjs release-contract`, then bootstrap the private release authority with `hmaint release bootstrap --repo <absolute checkout> --json`. Pass the numeric ci_run_id of a successful exact-SHA CI run so the verifier binds repository, workflow, branch, and head SHA.

How do I recover a failed Happier release run?

Apply the recovery table in skills/happier-ci-stabilize/SKILL.md: use native failed-job rerun for same-SHA transient failures, immutable-candidate resume after control or test-only fixes, or a fresh release when source, packaging, or signing inputs changed. Never blindly retry an ambiguous publication mutation.

Does the release preflight rerun the full CI test suite?

No. The preflight is cheap and non-mutating, validating only operation-specific inputs like source identity, version projection, credentials, and runner prerequisites. It consumes an existing successful exact-SHA CI attestation instead of repeating unit, typecheck, integration, or E2E work.

Can I publish a release from a dirty maintainer-tools checkout?

No. Bootstrap and preflight must bind the maintainer-tools commit and return structured admission failures before any release mutation. The checkout must not be modified or cleaned implicitly as part of releasing.

What happens to issue stage labels when a release reconciliation fails?

A reconciliation failure does not roll back published artifacts but remains a visible release-workflow failure. Retry only the idempotent label owner or leave issues at their prior stage; never close issues or claim availability without release evidence.