Skip to content

v0.123.0 — Reliability, recovery, and review workflows

Latest

Choose a tag to compare

@antiartificial antiartificial released this 11 Sep 02:34
· 12 commits to main since this release

This release completes the reliability and review work unit after v0.108.0. Versions v0.109–v0.122 remain unverified historical proposals; their identifiers are deliberately skipped.

Changes

  • Strict deployment modes and effective backend reporting.
  • Durable write/feedback recovery, stable idempotent writes, and Postgres coordination leases.
  • Correct DSL edge filtering and current graph hydration for ANN results.
  • Ranking-to-debugger navigation with retained fixture context and persistent browser baselines.
  • Acquisition candidates held outside the graph until explicit review.
  • Central review worker with dry runs, bounded rules/webhook evaluation, durable run audits, and manual failure handling.
  • Optional exact-token access control across REST, gRPC, GraphQL, and admin surfaces.
  • Updated Go, TypeScript, and Python APIs; client/CLI refactor; release docs and next steps.

Upgrade notes

Standard mode now requires a Postgres DSN; unsupported scaled mode fails explicitly. Recovery is eventual repair, not a cross-store transaction. Workers default to dry run and never automatically approve acquisition candidates. With no token registry configured, local unauthenticated behavior remains available; use the documented access-control configuration for network exposure.

Verification

Full Go tests/vet, focused race checks, live Postgres and authenticated HTTP workflows, real gRPC authorization checks, SDK contract tests, admin/docs builds, native container smoke, and browser ranking/baseline checks passed locally. Existing opt-in Python live-server cases were skipped separately.

CI for the released commit: https://github.com/antiartificial/contextdb/actions/runs/34554712765

The attached Linux amd64 binary and release-health evidence come from this CI run. Source archives are provided by GitHub. No npm/PyPI package publication or production service deployment is claimed.

Full release recap and next steps