One file per release, named v<MAJOR>.<MINOR>.<PATCH>-<landmark>.md —
v1.0.0-springer-mountain.md. ../RELEASING.md is the process;
§5 has the landmark order and §7 what goes in a file.
These files are canonical. The GitHub release body is generated from the file rather than the other way round, because a release body is editable in place with no history and lives in one company's database — and this project's whole stance is that a club can be handed the repository and carry on, which means the release history has to arrive in the clone.
A file here is generated by the Draft release notes workflow and then edited:
the draft carries TODO (human) markers for the things a generator cannot know,
and the release name, the historical figure and the paragraph that makes it a
release rather than a diff are the parts worth a person's time.
pages.yml refuses to deploy a tag that has no file here.
Not to be confused with the identically named releases/ prefix in the R2
bucket, which holds data releases — ../pipeline/R2_LAYOUT.md.
Two trains, one word; RELEASING.md §10 is where they touch.