Notable changes to Lark are documented here. The format is based on Keep a Changelog, and the project follows Semantic Versioning.
Pre-1.0: Lark is versioned
0.x. Breaking changes in0.xreleases are rare and always called out here; if a release changes the on-disk format, it ships with a migration path. Even so, back up before upgrading (see BACKUP.md) — downgrades aren't supported, so the way back from a bad upgrade is a restore. For how we think about1.0.0, see Project status in the README.
The first public release of Lark, a realtime database server that is also wire-compatible with the Firebase Realtime Database, comprising the lark-server database engine (thread-per-core Rust on Glommio/io_uring, per-database write-ahead log, the lark-blob on-disk format with lazy loading and incremental compaction, and tunable durability up to fsync-before-ACK), the lark-edge gateway in Go (TLS termination, WebSocket/WebTransport/REST transports, JWT auth across four token formats, an embedded admin dashboard), the Firebase security-rules language and query surface, per-database resource limits, and deployment, backup, and observability guides with a one-command Fly.io quickstart.
For what Lark is and how it's tested, start at the README and TESTING.md. Subsequent releases will list their changes here in the usual Added/Changed/Fixed form.