Skip to content

Release v0.2.0

Latest

Choose a tag to compare

@homer6 homer6 released this 16 Nov 07:33
918ebf1

Released 2026-11-16. A minor release, since v0.1.3: the repository is prepared for the Orama Lake open-source release. It is licensed MIT, has a security policy, pins its base images by digest, and its public tree carries nothing internal. The runtime's behaviour is unchanged from v0.1.3.

What it includes

PR Change
#31 SECURITY.md: how to report a vulnerability privately, and what we commit to
#32 The Dockerfile names its base images by multi-platform index digest as well as by tag, so a moved tag cannot change a later build of the same source
#33 Internal material kept out of the public tree: a public CONTRIBUTING.md, and the published files rewritten to name nothing internal
#34 MIT LICENSE and COPYRIGHT, an SPDX-License-Identifier: MIT line in every source file, THIRD_PARTY_LICENSES, CONTRIBUTING.md, CLA.md and CODE_OF_CONDUCT.md, and the software bill of materials (sbom.spdx.json, sbom.cdx.json, tools/sbom.py)
#37 The Dockerfile has one pinned build stage again: a merge had left a second, unpinned one (#36)
this release the version 0.2.0 and these notes; the SBOM regenerated

What it does not include

  • No pull request was open at the cut, so nothing was deferred.
  • No change to how Apps are loaded or served.

Known issues

  • The image is not published (#35, a release blocker for the open-source release). It is built on python:3.12-slim (Debian), which bundles GPL and LGPL userland (glibc, bash, coreutils, dpkg, readline). It moves to scratch or another static base with static binaries before the image is made public.
  • Earlier known issues: as in v0.1.3.

Verification

Proof Result
uv run pytest, Python 3.12 33 tests, all pass
tools/spdx-headers.py --check passes
tools/sbom.py --check passes, regenerated after the last change
uv lock --check the lock file matches pyproject.toml