Skip to content

v0.2.0

Choose a tag to compare

@Sannrox Sannrox released this 26 Jul 07:47
· 691 commits to main since this release
v0.2.0

Release notes: v0.2.0

Crate version: 0.2.0. Tag: v0.2.0.

Pair with release readiness.

Scope

Pre-1.0 minor release covering architecture ADRs 0001–0009 and product depth
through staged products, optional Postgres multi-tenant hub store, multi-replica
fencing, fleet ops, runtime inventory heartbeat, OpenMetrics, and outcome→prior
projection. No claim of 1.0 stability.

Open release-blocking issues at tag time: none.

Compatibility and migration

Surface Impact for 0.2
Crate version 0.1.0 → 0.2.0
SQLite SCHEMA_VERSION Unchanged; community path remains single-writer
Runtime / auth / federated / model / plan / catalog contracts Documented *_CONTRACT_VERSION / PLAN_FORMAT_VERSION remain 1
Optional Postgres hub Feature postgres; TENKAI_POSTGRES_URL; schema-per-tenant; not the community default
Multi-replica --replica-count > 1 requires store shared_replica_state; durable tick fence when Postgres is configured
high_availability capability Still not claimed by Postgres adapter; flag remains fail-closed without it
Defaults Signing/approval fail closed; tenant mode / enterprise flags default off

Operator upgrade notes

  1. Embedded / SQLite: rebuild binaries; existing .tenkai-state continues
    if schema version still matches. Run tenkaictl backup before major upgrades.
  2. Optional multi-tenant hub: enable postgres, set TENKAI_POSTGRES_URL,
    follow postgres-tenant-store.md. Do not
    co-locate IdP databases.
  3. Multi-replica hubs: follow
    multi-replica-hub-runbook.md. Prefer
    single active writer + shared durable fence; do not share community SQLite files.
  4. Development bypasses (--allow-unsigned-development,
    --allow-unapproved-development) remain explicit and audited — not
    production defaults.

Rollback

Previous binary + restore of Tenkai-owned SQLite backup (embedded) or Postgres
pg_restore (hub), then re-inject tokens from the secret store. Recovery never
depends on sekai-chisei.

User-visible changes

Added

  • Fleet status, fleet drift watch, multi-environment rollout waves
  • Environment capability facts + local hardware inventory probe
  • Runtime inventory fact heartbeat (POST …/inventory, optional disable)
  • Helm and native Kubernetes (kubectl) software apply paths
  • Model runtime control plane, llama.cpp reference path, canary × model_runtime
  • Staged products: policy_bundle, eval_suite, agent_definition
  • Optional advisory plan priors (local file + OutcomeProvider projection)
  • Remote HTTP GateProvider for chisei-compatible eval decisions
  • AuthStack management HTTP, federated identity accept path, JWT EdDSA assertion verifier
  • Tenant isolation on management HTTP surfaces; in-memory and optional Postgres tenant stores
  • Postgres hub shared_replica_state (single-active-writer), multi-host tick fencing, durable Postgres fence
  • Optional OpenMetrics scrape (--enable-metrics / GET /metrics)
  • Multi-replica hub ops runbook; ADR 0008 / 0009

Changed

  • README Status tracks second-gen fleet, hub, and staged-product surface
  • Capability negotiation remains fail-closed for multi-replica / HA / tenant flags

Security

  • Fail-closed signing, plan approval, tenant non-disclosure, and capability gates preserved
  • Diagnostics, metrics, and fleet baselines must not carry management/runtime tokens

Migration

  • Optional only: Postgres feature, multi-replica flags, metrics flag; community path unchanged

Out of scope for 0.2

  • Advertising product high_availability capability
  • Catalog service extraction
  • Identity-plane DB co-location