Skip to content

Releases

v0.1.0

Choose a tag to compare

@akkaraponph akkaraponph released this 21 Nov 09:00

Itervyn v0.1.0 release notes

Source revision: 1df3457b23096f3b9ab15f2e8aa7aa06bd3f9107.

Summary

  • Local CLI itervyn with init, doctor, verify, inspect, version.
  • Verification aggregates Invaris (native check profile invaris.dev/v1alpha2) and Evaris (imported-run evaluation) into fail-closed results.
  • New trusted configuration itervyn.config/v1alpha2 with external config, harness, provider and guard programs, and independent evidence destination.
  • New revision gate: --expect-revision <sha> (and project.requireCleanTree in v1alpha2 policy) records Git state before and after providers, compares it with native Invaris provenance, and blocks PASS on missing, dirty, moved or conflicting provenance. Live Invaris evidence is required by the gate; Evaris alone cannot satisfy it.
  • New result schema itervyn.result/v1alpha2 (gated results). v1alpha1 config and result remain supported.
  • CI revision-gate workflow (.github/workflows/revision-gate.yml) with read-only candidate mounts, cleared environment, trusted policy from an independent commit; a trusted AST guard rejects forbidden provider imports in internal/verify.
  • Launcher fix from the Panda implementation (.itervyn-policy/run-gate.sh): refuses pre-existing reserved harness file; stages exact trusted harness bytes.

Compatibility

  • Additive. Existing itervyn.config/v1alpha1 and itervyn.result/v1alpha1 are accepted unchanged.
  • Unknown schema versions or fields are refused (per docs/release.md).
  • Provider validation included Invaris v0.5.1 and Evaris v0.5.0; an Evaris v0.4.0 compatibility subset passed in earlier validation on a prior worktree. Older supported Invaris releases were not checked in that readiness assessment.
  • No evidence-store migration is promised (docs/release.md).

Known limits (see readiness)

  • Gate runs on a writable local filesystem have no same-user isolation.
  • The gate's trusted container can write evidence; future candidate-code execution needs a separate boundary.
  • No Evaris-to-candidate revision linkage is claimed.
  • Hosted GitHub pull-request and merge-queue revision-gate runs require maintainer bootstrap and a protected ruleset (docs/integration.md); those runs and setup were not performed. The separate hosted Verify workflow passed on the release commit.
  • Native execution was not verified on every released platform; the readiness assessment recorded only a macOS arm64 archive smoke test on an earlier worktree.
  • The readiness document records open release gates for older supported providers and native platform coverage; its provisional worktree and publication status predate the release commit.

Upgrade / rollback

  • Replace the binary; completed records are not rewritten. Old binaries reject unsupported records.
  • Evaris evaluations created before a failure are retained; no automatic deletion.