release-procedure

What problem does it solve?

This Skill prevents broken or inconsistent releases by providing an end-to-end, verification-first checklist for cutting, tagging, and publishing an alef version with correct changelog and synchronized version numbers.

Core Features & Use Cases

• Release readiness and safety checks: Runs pre-flight build and tests to ensure the release only ships when the repo is healthy.
• Changelog and version correctness: Requires moving entries from Unreleased into a dated release section and updates Cargo.toml, alef.toml, and ALEF_REV in lockstep via the Taskfile.
• Linting, atomic commit hygiene, and verified publishing: Enforces a prek lint pass, a single atomic release commit, and uses gh release create so GitHub release automation is triggered correctly.

Quick Start

Tell your release manager to run the full pipeline steps for a new alef version, starting with confirming the working tree and CI health, then updating CHANGELOG.md, setting the version via task set-version, linting with prek, committing chore(release): X.Y.Z, creating the annotated tag, and publishing with gh release create.