Repository navigation
Release v0.1.1
app-runtime v0.1.1
2026-10-26. A security fix on top of v0.1.0, released the same day, before v0.1.0 reached any cluster.
Everything in v0.1.0 is included. Image: oramasearch/app-runtime:v0.1.1 (private).
What it adds
- Identity only from Lake's forward auth (#14, fixes #13 / LSR-182 and #11):
current_user()readsX-Orama-User(a bare id or a JSON object) only whenAPP_AUTHis exactlylake.- The operator sets
APP_AUTHfrom the App'sspec.auth(orama-operator#831,
in v0.10.3). - On a Public App, an unset
APP_AUTHor any other value,current_user()isNone. - The unsigned fallbacks (
X-Orama-User-Id,X-Orama-User-Email,X-Orama-User-Name,X-Auth-Request-*) are
removed. CurrentUserMiddlewarestrips forgeable identity headers before App code or Streamlit (HTTP and WebSocket) sees
them.ORAMA_CURRENT_USERis honoured only whenAPP_AUTHis unset (local development).
Rollout order
The operator must set APP_AUTH before this runtime runs. Under an older operator, current_user() is None on every
App: it fails closed. Every cluster runs orama-operator v0.10.3, which sets it, and the live App pods carry
APP_AUTH=lake.
Known issues
- #12: the pre-launch security review's other findings for the
runtime.
Verification
| Proof | Result |
|---|---|
Full suite (uv run pytest, macOS) |
31 passed, 0 failed, 0 skipped |
| #14 after its rebase onto dev | 31 passed, including the Streamlit stream test from v0.1.0 |
| Version test | tests/test_release.py reads 0.1.1 from pyproject.toml and requires this page |
| Image | built from the tag on the cluster BuildKit (linux/amd64) |