897779b925
The first README fence becomes two labelled, copyable commands — the RIG_REF=main development command first (byte-identical to before, so the #89 guard at test/cli.sh:514 still passes) and the bare latest-release command below it, each preceded by a comment line naming its channel. Refs #149 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 63.md | ||
| 95.md | ||
| 103.md | ||
| 105.md | ||
| 106.md | ||
| 109.md | ||
| 110.md | ||
| 112.md | ||
| 119.md | ||
| 120.md | ||
| 123.md | ||
| 133.md | ||
| 136.md | ||
| 149.md | ||
| README.md | ||
changelog.d/ — the next release's section, one fragment per issue
Machine-assembled by bin/changelog-assemble (#112): every PR that changes
behavior writes one file here — <issue>.md, the exact prose that will be
published, nothing else — and the release PR folds them all into the next
## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct
filenames never conflict, which is this directory's whole reason to exist.
This README is the marker that keeps the directory tracked when it holds no
fragments (#112 D1) — changelog-armed refuses a tree without it; do not
delete it.