changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42 releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases (none has been published; its README says how one would be filed). CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly as it was, and a table per major version (version, date, edition) that links each file. Each file is its section, copied byte for byte except that its heading is the file's H1 (so the sub-headings move up one level, outside code fences), relative links gain ../../../ so they name the same repository paths, and the --- separators between sections are gone. Checked by reversing all three changes on every file and comparing with the original section: 40 of 40 equal. Two releases had no section: v1.0.0 (its GitHub release notes, which the changelog pointed to as "Initial stable") and v1.1.3 (its tag message). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
604 B
604 B
Changelog files
One file per release, newest version first in the index:
CHANGELOG.md at the root lists them all, with what is not
released yet.
v<major>/<major>.<minor>.x/<version>.md- a release, e.g.v4/4.7.x/4.7.1.md. Its first line is the release heading; the rest is the release notes, which is also what the GitHub release of that tag says.beta/- pre-releases (none so far).
A file is written once, when its version is released, and is not reworded afterwards: it records what was true then, links and file names included.