9.3 KiB
Changelog
All notable changes to FrameLedger are documented here.
Format: Keep a Changelog.
Versioning: Semantic Versioning — MAJOR
bumps for a database schema or IPC protocol break (docs/11_UPDATER.md).
release.yml reads the section for the tag being released (tools/release-notes.ps1) and
uses it as the GitHub release body. A missing or empty ## [x.y.z] section is a red
release, not an empty note — so cutting a release means moving the [Unreleased] entries
under a ## [x.y.z] - date heading in the same commit that bumps VERSION, then tagging
(docs/13_CI_CD.md §Branch & release policy). (For a pre-release, vX.Y.Z-beta.N, VERSION already holds the
numeric core and does not move; the heading is the full version — corrected 2026-10-04.)
Built 2026-09-14 (P4 PR-5). From 2026-08-06 until then this paragraph said the workflow "will" exist and that a missing section "will mean an empty release note"; the second half was the wrong design and is replaced rather than implemented.
This file still has no## [x.y.z]heading: the first one is the owner's, in the commit that cuts the first tag.The first heading is
## [0.1.0-beta.1](2026-09-16), and it is a summary rather than the moved entries. The instruction above says "move the[Unreleased]entries under the heading"; by the first tag those entries were 370 KB — every PR since 2026-08-04 — and a GitHub release body holds 125,000 characters. So the versioned section is a written summary of what the pre-release is and is not, and the entries it summarises stay below it, verbatim, under a heading that is not a version (## Ledger before 0.1.0-beta.1), whererelease-notes.ps1stops reading. From the second tag on, the entries under[Unreleased]are short enough to move as written.
Split 2026-10-19 (beta.24, owner decision D66). Each released section now lives in its own file under
docs/changelog/, moved verbatim, and the ledger kept before the first tag in five parts underdocs/changelog/ledger-before-0.1.0-beta.1/; the table below lists them all. This file keeps[Unreleased], where every pull request adds its entry (tools/changelog-check.ps1looks for this file).tools/release-notes.ps1readsdocs/changelog/<version>.mdfor the tag being released, so cutting a release moves the[Unreleased]entries into that new file — under its## [x.y.z] - dateheading — and adds its row to the table, in the commit that is tagged.
Unreleased
Documentation
- 0.1.0-beta.50's release facts are recorded (
docs/HANDOFF.md§Left open by this session): the run, the eight assets and their digests, the build id in the five native libraries, the delta, the wiki, the rehearsals, what SonarCloud and Qodana said of the released commit — and that the release shows two dates, the owner's day in the documents and UTC's on GitHub and in the legal texts.
Releases
Newest first. Each file holds that release's section exactly as it stood here.
The ledger kept before the first tag (2026-08-04 → 2026-09-16), every pull request in full, newest first:
docs/changelog/ledger-before-0.1.0-beta.1/part-1.md— 455 linesdocs/changelog/ledger-before-0.1.0-beta.1/part-2.md— 805 linesdocs/changelog/ledger-before-0.1.0-beta.1/part-3.md— 954 linesdocs/changelog/ledger-before-0.1.0-beta.1/part-4.md— 990 linesdocs/changelog/ledger-before-0.1.0-beta.1/part-5.md— 1218 lines