Skip to content

Release v0.3.1

Latest

Choose a tag to compare

@homer6 homer6 released this 16 Nov 08:24
4bc4b5b

Released 2026-11-16. A patch release. One clean header in the Dockerfile, since v0.3.0. Nothing the runtime does has changed. Image: docker.io/oramasearch/agent-runtime:v0.3.1.

This release is the tree of dev after #45 (ccadaaf), with these notes and the version.

What changed

Every pull request merged into dev since v0.3.0 (git log --first-parent v0.3.0..origin/dev):

PR What it does
#44 Records the v0.3.0 image digest in the v0.3.0 notes; documentation only
#45 Gives the Dockerfile one clean header: the duplicated description is removed, and the comments no longer reference internal issues

No source file under src/ changed, and no setting is new or removed (git diff v0.3.0..v0.3.1 -- src is empty).

Not included

  • Claiming tasks by reference and naming the task on every call (#36): deferred for review, not in this release.
  • Unchanged from v0.3.0 otherwise.

Known issues

Security-relevant first. Unchanged from v0.3.0.

  1. Service turns write every tenant's trace to the shared pod's disk (#38): a service turn's trace (the message, the answer and every tool observation) is written under TRACE_DIR and never removed.
  2. The image bundles GPL and LGPL code (#40): it is built on python:3.12-slim (Debian: glibc, bash, coreutils, dpkg, readline). The move to scratch with static binaries is deferred; it is noted here and does not block this release.
  3. Dataset-confined launch credentials are not yet confined at Lake: the runtime refuses what it cannot prove, but the launch token itself still carries the person's reach.
  4. The bus client is not yet the workspace-aware cutover client (#6): no workspace_id on every call, no lease renewal, no idle backoff.
  5. One test fails (#41): tests/test_lake_bus.py::test_a_task_is_claimed_run_and_answered_on_the_bus still expects a bus turn's body without the claim that v0.3.0 added. The behaviour is the intended one; the test was not updated with it.

Where it has run

The v0.3.1 tree had not run on a development environment when it was released. It differs from v0.3.0 only in Dockerfile comments. Lakes take the operator's default runtime image; moving it to :v0.3.1 is a separate operator change.

The image

Built from the tag v0.3.1 (4bc4b5b) with BuildKit (linux/amd64, the repository's Dockerfile), then tagged :v0.3.1 on that digest without rebuilding:

docker.io/oramasearch/agent-runtime:4bc4b5b@sha256:166a83183de2e7eaa368c67f8eb1def327641815a6690f9c824c4e850882f654, also tagged :v0.3.1 (same digest). The image is published on Docker Hub; its GPL/LGPL base is a known issue (#40).

Pinning it on a Lake is a separate change to the operator's defaults or the Lake's resource.

Verification

Proof Result
Test suite (uv run --frozen --group dev pytest -q -ra, macOS arm64, Python 3.12) 149 tests: 148 passed, 1 failed (#41, fails alone too), 0 skipped. tests/test_dataset_work_area.py 45, tests/test_skills.py 31, tests/test_runtime.py 25, tests/test_service_auth.py 13, tests/test_conversations.py 9, tests/test_turn_destinations.py 9, tests/test_bus_backpressure.py 6, tests/test_lake_bus.py 4 (1 failed), tests/test_mcp.py 4, tests/test_release.py 3
Skills contract (tests/test_skills.py, in the suite) Passed: every capability in the vendored Lake OpenAPI is accounted for; skills.json matches skills.py
Version pyproject.toml and uv.lock 0.3.1; importlib.metadata.version("agent-runtime") and GET /healthz report it (tests/test_release.py)
SPDX headers (python3 tools/spdx-headers.py --check) Passed
SBOM (python3 tools/sbom.py --check) Passed, regenerated for v0.3.1
Live agent runs (a model through Lake's gateway) Not run for this release (needs a live model)
Dev environment Not run (above)
Linux image build (BuildKit, from the tag) Built from v0.3.1: oramasearch/agent-runtime:4bc4b5b, also :v0.3.1, sha256:166a83183de2e7eaa368c67f8eb1def327641815a6690f9c824c4e850882f654