The changelog
Every release below had to earn its tag. A version’s goals — a list of accepted requirement identifiers — are locked before the work starts, and the release gate refuses to tag until each one is both cited by a merged pull request and marked done in the implementation status. So the list under a version is not a summary of what happened to land; it is the set the release was measured against.
That is why this page counts requirements rather than commits. A commit log says what was written. The locked goals say what was promised, and the count beside each release says how much of it was proved.
The list is read from the revisions at the foot of this page, so it is every release as of those and not as of this morning. A version tagged after them appears here when the pins move.
What shipped
Section titled “What shipped”0.13.0Milestone M9Released 2026-09-09Changing your mind — reconfiguration, migration, clean uninstall, and credential management.
0.12.0Milestone M8Released 2026-09-07Living within limits — disk space, retention, bandwidth and scheduling.
0.11.0Milestone M8Released 2026-09-04The household asks — the request flow, identity and invitations, and guidance to a client app.
0.10.0Milestone M7Released 2026-08-27The front door and what guards it — the web UI's security and binding policy, the entry surface, and the privacy stance.
0.9.0Milestone M7Released 2026-08-26Speaking plainly — interface tiers, the plain-language layer, and progressive disclosure.
0.8.0Milestone M6Released 2026-08-22Operating a running stack — forms and partial stacks, lifecycle control, log viewing, and the diagnostics that tie them together.
0.7.0Milestone M5Released 2026-08-21Trust checks, part two — provider health and quota, the support bundle, and the auto-remediation that acts on what the checks find.
0.6.0Milestone M5Released 2026-08-16Trust checks, part one — VPN egress and killswitch proof, storage and hardlink verification, and queue health with its stuck-item categories.
0.5.0Milestone M5Released 2026-08-09How the product speaks — the error and remedy vocabulary every finding is worded in, the notification channel that reaches the operator without being sought, the health summary, and the dashboard's data model. The foundations the trust checks are expressed in terms of, so they exist before the checks that need them.
0.4.0Milestone M4Released 2026-08-08Auto-wiring & seed — closes M4's wiring: the tool reads each service's config, wires them together, and proves the pipeline end to end.
0.3.0Milestone M4Released 2026-07-310.3.0 — M4, first slice: backup & restore.
0.2.0Milestone M3Released 2026-07-30M3 — the setup wizard. The product-thesis milestone: a fresh machine reaches a
0.1.0Milestone M2Released 2026-07-26The bootstrap release — the baseline the train governs from. Goals are the
Downloads and release notes
Section titled “Downloads and release notes”Binaries, checksums and attestations are attached to each tag on the forge, and the install instructions that come with them are generated per release. Start from installing lemonfiber, or go to the releases themselves for a specific tag.
Where this comes from
Section titled “Where this comes from”- The version train — how a release is staged, gated and finalised
- The version manifests — one file per release, and what it must contain
- The roadmap — the versions still ahead
- What is built — the per-deliverable record the gate reads
Read from the revisions this site pins:lemonfiber/spec at 1d10402, 2026-09-09 · lemonfiber/lemonfiber at a2ac9bf, 2026-09-09