Versions & releases
Drafts, published snapshots, change notes and releases.
The lifecycle
- Draft — a new list starts as a draft, visible only to you. Edits happen in place; drafts never create versions.
- Publish — takes an immutable snapshot: version N. The list page always shows the current version; older versions remain browsable in Versions.
- Edit again — editing a published list works on a working copy; the next publish produces version N+1 with a change note.
Change notes work like commit messages. You can write one yourself or let AI generate it from the diff between versions.
Releases
Versions are cheap and automatic; releases are deliberate. A release marks a
specific version with a tag (default vN), a title and markdown notes — exactly
like GitHub Releases. Use them to signal "this revision is the one to follow".
Under the hood: git
Every list is backed by a real git repository where each version is a commit
touching list.json. That's why versions are immutable, diffable and
cloneable — see Git access.