Repository navigation
Conversation
Ported from agent-ask-orama#47: receive nothing while every worker is busy, leave tasks this replica cannot run unclaimed on the bus, cap one customer at AGENT_BUS_TENANT_WORKERS workers, and keep at most 256 dispatch rows waiting. run_task is unchanged. README and tests/test_bus_backpressure.py. Refs #33
Private reporting to security@orama.com, with response targets of 2 business days, 7 days and 90 days. G1 of oramasearch/orama-bridge#273.
Both python:3.12-slim stages and the uv image are named by tag and multi-platform index digest, so a moved upstream tag cannot change what a rebuild of the same source contains. The README says so. Refs oramasearch/lake#1003
…ntributor docs Add the MIT LICENSE and COPYRIGHT (Orama Search Inc.), an SPDX-License-Identifier: MIT line in every source file, THIRD_PARTY_LICENSES, CONTRIBUTING.md (DCO sign-off, no CLA) and CODE_OF_CONDUCT.md (Contributor Covenant 2.1), for the open-source release's license gate. Regenerate: - headers: python3 tools/spdx-headers.py (idempotent; --check lists files without one) - third-party notices: `uv export --frozen --no-dev` of uv.lock, installed into a scratch venv, then `pip-licenses --with-license-file --with-notice-file` (runtime dependencies only)
The exact legal name, from Steve on 2026-11-15, replaces "Orama Search Inc." in LICENSE, COPYRIGHT and the notices.
tools/sbom.py writes sbom.spdx.json (SPDX 2.3) and sbom.cdx.json (CycloneDX) from the files git tracks at one commit: the packages syft finds in the lock files, plus the C and C++ components of the third-party license list, the git submodules and the Dockerfile base images. The creation time and namespace come from the source commit, so the files are reproducible; python3 tools/sbom.py --check says when they are stale.
… of the DCO CLA.md assigns the copyright in each contribution to OramaSearch, Inc., with a fallback exclusive licence where an assignment is not effective, a licence back to the contributor, a patent licence, and an entity version for employers. A contributor signs it once, electronically, through a bot on their first pull request. CONTRIBUTING.md, README.md and COPYRIGHT describe it in place of the DCO sign-off.
docs: add a security policy (SECURITY.md)
fix(build): pin the base images by digest (lake#1003)
fix(security): claim a bus task only when a worker is free (LSR-075)
chore(license): MIT license, SPDX headers, third-party notices and contributor docs
…e's claim (LSR-076, LSR-008) Conversations live in conversations.Conversations, bounded by count, turns, bytes, total bytes and idle time (ported from agent-ask-orama#48). A bus turn's conversation is kept under the account and workspace of Lake's claim reply (lake_bus.turn_body), never under ids in the body; a direct turn is kept apart. A turn that raises is rolled back. README and tests/test_conversations.py. Refs #34
fix(security): bound the conversation memory and key bus turns by Lake's claim (LSR-076)
Add .public-exclude (AGENTS.md and agent folders stay private) and take internal material out of the files that will be published: issue and pull request links, security finding ids, cluster, set and environment names, the hostname of the App that prompted the v0.2.2 fix, a quoted and a paraphrased instruction, and "private repository and image" wording.
CLAUDE.md and AGENTS.md are no longer kept out of the public export: .public-exclude listed only them, so it is removed. The agent files are rewritten to be public (build and test commands, conventions, the architecture rules); the Orama-internal rules moved to the private umbrella bridge.
docs: prepare the tree for the public export (G3)
docs(release): v0.3.0 notes and version
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What: Promotes
devtomainas agent-application v0.3.0.Why: Steve asked to cut the release (2026-11-16).
How: A merge commit of
devintomain; the tagv0.3.0goes on it, then the GitHub release and the image built from the tag.Notes: https://github.com/oramasearch/agent-application/blob/dev/docs/releases/v0.3.0.md
Included
SECURITY.md)Not included: #74 (claiming tasks by reference, lake#871), deferred for review.
Known issues
python:3.12-slim), so it is not published.buildstages; the one that builds the venv is unpinned.Verification
Full suite: 102 passed, 0 failed, 0 skipped.
tools/spdx-headers.py --checkandtools/sbom.py --version v0.3.0 --checkpass.Where it runs, and after the merge
Not run on a development environment. After the merge: tag
v0.3.0, the GitHub release, the image built from the tag and pushed to its Docker Hub repository with thev0.3.0tag on the same digest. Nothing is rolled to a cluster.