v0.2.7
v0.2.7 fixes --readonly recall on Windows and when using a relative --data-dir path.
Fixed
- Resolve and encode SQLite file URI paths correctly, including Windows drive letters, spaces, Unicode,
#, and%. This resolves the misleadingSQL logic error: out of memory (1)failure in #123. - Preserve the readonly snapshot contract: database writes remain rejected, recall counters and oplog stay unchanged, and no WAL/SHM sidecars are created. There is no fallback to a writable connection and no database schema or file-format change.
The fix is included in PR #125, with native Windows and Linux CI coverage.
--readonly still assumes an immutable, static snapshot. It should not be used to follow a database that another process is actively changing.
Downloads
Archives are available below for macOS, Linux, and Windows, each on amd64 and arm64. Verify the download against checksums.txt. Existing Homebrew Cask users can update with brew upgrade --cask mnemon.
Verification
- Linux and native Windows CI passed for release commit
aab97af8002bf0c8ac18d88da64293e41c9eb121. - The release workflow passed, publishing all six platform archives and updating Homebrew.
- All archive SHA-256 values and binary CPU architectures were checked. The published macOS arm64 binary passed readonly query, rejected-write, and readonly-permission smoke tests without changing database bytes or creating sidecars.