Skip to content

Jevia 0.1.6

Choose a tag to compare

@github-actions github-actions released this 30 Sep 06:21
· 80 commits to main since this release
c6d22e3

Jevia 0.1.6

CLI/core 0.1.6 and the separately versioned Node SDK 0.1.2 are published.

Highlights

  • Automatic execution recording for jevia run, with supported Claude Code, Codex, and OpenCode native adapters. Extra verification and feedback are optional; observed activity is not proof that a task succeeded.
  • Durable live checkpoints, recoverable journals, whole-session counters, and shutdown-failure protection.
  • Explicit lock release despite duplicated/inherited Unix descriptors, preventing false-active recovery failures and delayed history/cache unlocks.
  • Read-only jevia harness health <name> diagnostics and passive model activity/coverage in jevia stats.
  • Optional SDK recordExecution() for finished application-owned work, with application provenance, bounded input, exact-retry idempotency, and JSONL/SQLite/PostgreSQL support. Recorded history informs subsequent routing and its cache keys automatically.
  • Contract tests against pinned real harnesses and local model endpoints without bypassing normal hook trust.

Upgrade notes

Back up history and upgrade all readers/writers sharing a store together to CLI/core 0.1.6 and SDK 0.1.2. New records use schema 6; schemas 1–5 remain readable. SQL database schema 1 is unchanged. Older clients reject newer records: do not downgrade against updated history.

Omitted auto_verify now defaults to false (CLI 0.1.4–0.1.5 defaulted to true). Existing explicit verifiers and opt-in settings remain enabled.

This experimental patch adds Rust struct fields and enum variants and is not source-compatible with every 0.1.5 library caller. Review direct struct construction and exhaustive matches. Minimum versions remain Rust 1.92 and Node.js 20.

Install

cargo install jevia --version 0.1.6 --locked
npm install jevia@0.1.2

The npm package requires the CLI and does not download it automatically. Release binaries include checksums, an SPDX SBOM, and signed GitHub build/SBOM attestations. The default web installer advances through a separate PR only after its platform smoke tests pass.

See the changelog, CLI reference, and SDK recording guide.