Releases

Every StoryLark release gets a version number and a human-readable set of notes. The sidebar lists every published release, newest first.

How versioning works

App version = storylark-core. The version an app shows on its About screen is the exact npm release of the engine it was built from. The notes for that number on this site describe precisely what that app can do.
Companion packages version separately. storylark-worker (the sync/API worker) and storylark-pipeline (the publishing pipeline) have their own numbers; an app's About → Version & build lists whichever are part of its build.
Every build is traceable. About → Version & build also shows the site build's git commit and build time, so any installed device can be matched to an exact release and deployment.
Two changelogs, one source of truth. These pages are the curated, human-facing notes. The auto-generated, per-commit technical changelog lives in the repository.

StoryLark's stable foundation, plus a private shelf for documents you bring yourself.

My Library — on presentations that enable it, add PDF, DOCX, text, pasted text, or an accessible web page from Library. Personal documents stay on that device and never enter a publisher's content store or account sync
Read or listen — imports use the normal Reader and the browser's device voice; Keep screen awake now also covers visible device-voice playback
Portable by choice — export and restore a personal-library JSON backup without silently enabling cloud sync
Stable 1.0 contracts — the supported brand, presentation, deployment, content, package, and adapter surfaces now have an explicit compatibility policy
Release gate — every pull request and main-branch change must typecheck, build, and pass the automated suite before release

Found a gap? StoryLark is open source — improve these notes on GitHub.