publishlisted

# /evo:publish > Canonical release entry point. Owns the full publish lifecycle: pre-flight → bump → changelog → ship → propagate → rollback-on-failure. NOT a synonym for "git push" — see [docs/release-protocol.md](../../docs/release-protocol.md) for vocabulary. ## What this skill does When the user types `/evo:publish 18.5.0` (or similar), invoke the go-native release pipeline with the target version. The pipeline owns every step (implementation: `go/internal/releasepipeline/`, journal under `.evolve/release-journal/`): | Step | Operation | Failure → action | |---|---|---| | 1 | Pre-flight gate (`evolve release-preflight`) | exit non-zero; abort, no mutations | | 2 | Auto-changelog | abort | | 3 | Version bump (6 markers) | abort | | 3.5 | Rebuild tracked binary `go/evolve` | abort | | 4 | Consistency check (`evolve release-consistency`) | abort, files in working tree | | 5 | Atomic ship | abort, nothing pushed | | 6 | Marketplace propagation poll (up to 5 min default) | auto-rollback unless `--no-rollback` | | 7 | Cache refresh | logged WARN; manual fix | > Steps 1–7 are the **`gh`-free** pipeline binary. It cannot see GitHub CI — it ends by printing a `NOTE: GitHub CI is NOT verified by this pipeline` advisory. CI gating is **this skill's** job (next section); never treat a green pipeline as a green CI. ## CI gating (this skill adds what the binary cannot) `evolve release` is self-contained and headless-safe, so it does **not** verify GitHub CI. This skill wraps the