Repository navigation
Released 2026-11-16. A patch release. The README no longer references internal issues, since v0.3.0. Nothing the agent does has changed. Image: docker.io/oramasearch/agent-autosuggest:v0.3.1.
This release is the tree of dev after #41 (e89830a), 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 |
|---|---|
| #40 | Records the v0.3.0 image digest in the v0.3.0 notes; documentation only |
| #41 | Cleans the README: the internal issue references are removed, and a duplicated line in A turn keeps nothing on the pod is dropped |
No source file under src/ changed, the Dockerfile is unchanged, and no setting is new or removed (git diff v0.3.0..v0.3.1 -- src Dockerfile is empty).
Not included
- Claiming tasks by reference and naming the task on every call (#34): deferred for review, not in this release.
- Unchanged from v0.3.0 otherwise.
Known issues
Security-relevant first. Unchanged from v0.3.0.
- The image bundles GPL and LGPL code (#37): it is built on
python:3.12-slim(Debian: glibc, bash, coreutils, dpkg, readline). The move toscratchwith static binaries is deferred; it is noted here and does not block this release. - Library agents hold live task credentials for every tenant they serve: one shared pod runs every tenant's turns with their task credentials.
- The workspace is not passed explicitly (#11): the agent sends only
customer_idon its reads, never the task'sworkspace_id. - The lease is kept by activity only. Lake renews a claim's lease on every capability call made with the task credential, so a turn is reclaimed only if one step outlasts
lease_seconds. Not observed. - The command line validates without workspace evidence (#14).
- Corpus drafts fail validation: the corpus's examples do not choose a registry level for S-1. The image keeps the
a882954corpus.
Where it has run
The v0.3.1 tree had not run on a development environment when it was released. Lakes take the operator's default image; moving it to :v0.3.1 is a separate operator change.
The image
Built from the tag v0.3.1 (c630000) with BuildKit (linux/amd64, the repository's Dockerfile, with the same contexts as v0.3.0: the catalog context catalog-cf20d264 and the corpus context agent-autosuggest-corpus-a882954), then tagged :v0.3.1 on that digest without rebuilding:
docker.io/oramasearch/agent-autosuggest:c630000@sha256:8908162a6d34a8a928fd41c18b8a50c5033d5fb7a623d20491e3ae06640e682f, also tagged :v0.3.1 (same digest). The image is published on Docker Hub; its GPL/LGPL base is a known issue (#37).
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, on the release branch) |
78 tests: 78 passed, 0 failed, 0 skipped. test_service.py 17, test_turn_destinations.py 15, test_service_auth.py 13, test_lake_1153_shapes.py 7, test_bus_backpressure.py 6, test_solution_evals.py 5, test_lake_bus.py 4, test_apps.py 3, test_solutions.py 3, test_app_evals.py 2, test_release.py 2, test_catalog.py 1 |
| Offline evals (no model) | evals/runtime-solutions.jsonl and evals/data-apps.jsonl, run through enforcement and validation inside the suite above; all pass |
| Version | pyproject.toml and uv.lock 0.3.1; the installed package reports it and these notes exist and are indexed (tests/test_release.py) |
SPDX headers (python3 tools/spdx-headers.py --check) |
Passed |
SBOM (python3 tools/sbom.py --version v0.3.1 --check) |
Passed, regenerated for v0.3.1 |
| Live-model evals | Not run (needs a live model) |
| Dev environment | Not run (above) |
| Linux image build (BuildKit, from the tag) | Built from v0.3.1 (c630000): oramasearch/agent-autosuggest:c630000, also :v0.3.1, sha256:8908162a6d34a8a928fd41c18b8a50c5033d5fb7a623d20491e3ae06640e682f |