release-processlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Release Process ## First: does this repository release with `basicly`? This skill describes `basicly release`, and it projects into every repo that installs the catalog — including one that cuts releases its own way. Check before following anything below: ```sh ls changelog.d/ 2>/dev/null; grep -n "## \[Unreleased\]" CHANGELOG.md ``` **If either is missing, this repo does not use `basicly release`. Stop, and follow the repo's own release document** (`docs/releases.md` or the equivalent). A consumer session read this skill as authoritative and nearly created a `changelog.d/` fragment and an `[Unreleased]` heading that nothing there consumes, then ran a command that did not match that repo's version single-sourcing. The repo's own evidence beats a projected skill, and the rest of this page assumes both files exist. ## Run `basicly release` — never hand-run the steps it performs Everything up to and including the annotated tag is one command: ```sh basicly release 0.6.0 --issue <record-id> --dry-run # pre-flight; writes nothing basicly release 0.6.0 --issue <record-id> # bump, pins, regen, changelog, commit, tag ``` It bumps the single-sourced `__version__`, regenerates the version-stamped projections, rewrites the `vX.Y.Z` install pins in `README.md`, `site/index.html`, both `.scripts/bootstrap.*` shims and every page under `docs/how-to/` — a glob, because the en