forked from heavy-duty/ceremony
changelog.d/253.md landed on main after this branch's point with the cite trailing the period — the crew#309 shape, the fifth fragment to arrive with it since #262 measured two. The criterion is that changelog.d/ is clean at the head, and the head CI reviews is the merge with main, which is where this one surfaced. Refs #262. |
||
|---|---|---|
| .. | ||
| 218.md | ||
| 230.md | ||
| 231.md | ||
| 232.md | ||
| 236.md | ||
| 237.md | ||
| 238.md | ||
| 241.md | ||
| 242.md | ||
| 247.md | ||
| 248.md | ||
| 251.md | ||
| 252.md | ||
| 253.md | ||
| 254.md | ||
| 258.md | ||
| 260.md | ||
| 262.md | ||
| 272.md | ||
| 276.md | ||
| 280.md | ||
| README.md | ||
| shape | ||
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. The shape sentinel beside it declares the set's shape —
grouped here, so every fragment carries ### headings (#182).