← ClaudeAtlas

release-checklistlisted

Run pre-tag verification and walk through the heimdall release pipeline. Mirrors .github/RELEASING.md so a release cannot silently skip a step. Use when the user explicitly asks to cut, prepare, or verify a heimdall release.
po4yka/heimdall · ★ 0 · AI & Automation · score 73
Install: claude install-skill po4yka/heimdall
# heimdall release checklist A guided release run. The skill is **user-invoked only** — releases are intentional, network-visible actions that must not happen as a side effect of unrelated work. The canonical source is [`.github/RELEASING.md`](../../../.github/RELEASING.md). This skill is the executable companion. ## Inputs Ask the user for: - The new version (`v0.x.y` or `v0.x.y-rc.N` for pre-release) - Whether to run the smoke workflow before tagging (default: yes for any release-sensitive change) ## Phase 1 — pre-flight (local) Run these in order. Stop on the first failure and surface the output. ```bash # Working tree must be clean git status --porcelain # Must be on main and up to date with origin git rev-parse --abbrev-ref HEAD git fetch origin main git status -uno # Full Rust verification cargo fmt --check cargo clippy -- -D warnings cargo test # Dashboard verification (only if src/ui or input.css changed since last release) ./node_modules/.bin/tsc --noEmit npm run build:ui git diff --exit-code src/ui/app.js src/ui/style.css # must be clean — committed artifacts must already match source ``` If `git diff` flags `app.js` or `style.css`, the user forgot to rebuild before committing. Stage and commit them as a fix-up before continuing. ## Phase 2 — version bump 1. Edit `Cargo.toml` `[package].version` to the new value. 2. Run `cargo build` to refresh `Cargo.lock`. 3. Confirm the diff is **only** `Cargo.toml` and `Cargo.lock` (and only the `version`/checksum