Repository navigation
Release v0.8.1
v0.8.1
2026-10-27. A patch release: the fixes from Steve's customer-insights demo on us.lake.live
(lake#1260).
What it includes
- A file's text is its exact UTF-8 (lake#1238,
#1265).repository_file(REST and MCP),resolve_model_file
andresolve_dataset_fileanswercontentsas the file's exact text withbinary: false; a file that is not
UTF-8 has nocontentsandbinary: true. Before, every non-ASCII byte came back as literal\xNNtext, and an
agent that committed what it read wrote the escapes into the file. The drive preview,diff_drive_versions,
/file/rawand/file/download, methodology sources and the model card use the same rule
(repositories). Clients:contentsis absent for a binary file. - Clustering never groups by a row number, an identifier or contact details
(lake#1242, #1264).
Columns named like a row number or id are identifiers; clustering also leaves out row numbers recognised by their
values, free text, names and contact details, and turns a date into its month and its days before the latest.
With nothing left it refuses, saying why for each column. The demo's "low Index / high Index" segments came from
this. - Predict on a clustering model (lake#1243,
#1267). The Model page shows a clustering model's segments and
tables, and Try it becomes Place a Row in a Segment. Against this release's Zetta pin the engine cannot place a
new row yet, andpredict,scoreandexplainsay so in plain words (not_supported) instead of a schema
error; zetta #1499 adds it, in a later Zetta release. - Change App reloads onto the new version (lake#1259,
#1262). The split screen's frame reloads again over the minute
after the App reads Ready, because the operator reported Ready while the old pod still served (fixed in
orama-operator #1050). A confirmed proposal now says
so. New browser checktools/e2e/change-app.mjs. - End-to-end fixes: T3 ranks only at-risk tables that have
accountandrisk
(lake#1258, #1263);
T12 studies a dataset keyed by a column the study engine recognises
(agent-experiments#32,
#1261). - The test runner's stale-database sweep no longer breaks a test's connection
(lake#1254, #1266).
Released with it: agent-application v0.2.7 (files read exactly, agent-application#63; filters applied everywhere,
agent-application#64), app-runtime v0.1.3 (Streamlit messages over 1 MiB, app-runtime#26: the demo App's filter),
and orama-operator v0.10.6 (Ready only when the rollout is complete).
Not included
- The Zetta release with zetta#1499 (placing a new row in a segment).
- zetta#1498: a study cannot name its entity column.
Known issues
As in v0.8.0, less those fixed above.
Verification
Each pull request ran lake's full native suite on a fresh local database with a regression test that fails on the old
code: #1265 1643 passed of 1672 (28 skipped need a live Zetta or outside service), #1266 1642 of 1671, #1264 1674 of
1674; #1267 its new test and all 52 Workspaces tests (its full run hit a broken local test template, since removed);
the frontend 469–471 on each.
The release (tag v0.8.1, 2e6024cf): lake's full native suite on a fresh local database: 1678 run, 0 failed,
28 skipped (they need a live Zetta or another outside service), 1 disabled (SearchBenchmark). The image
oramasearch/lake:main-2e6024cf = v0.8.1, sha256:fbb7b502b516ac15ecc1543a3aa21db6d2bc5a52636f9267d9c21517b8c3869c,
built from the tag on the cluster BuildKit, private. Not run: the Linux lane on the release (the affected tests of
#1265 ran there, 14/14).
Where it runs
dev and testing (2026-10-27); staging after the e2e gate on testing. Not production.