← Back to blog
Release essay2026-05-22

Ota v1.6.15 Now available

v1.6.15 hardens selected-mode execution, service proof reliability, and runtime-proof diagnostics for safer automation.

Idea

v1.6.15 is an execution-truth release.

The failures we saw were not about missing features. They were about boundary drift on real run paths: selected container mode could degrade to native in edge paths, detached service proof could report false readiness, and runtime-proof signals could be noisy for operators and CI.

This release closes those gaps by keeping selected execution intent explicit, proof signals consistent, and failure diagnostics actionable.

Feature

v1.6.15 ships practical hardening across execution, proof, and operator feedback:

  1. Mode-preserving rerun guidance: captured failure hints from ota run now keep effective mode context (for example container reruns stay container-focused).
  2. Container dependency execution fidelity: ota run --mode container now executes dependency branches on container backends when declared, instead of silent native fallback.
  3. Corepack run-path activation: Corepack-owned package-manager entrypoints (such as pnpm) are activated on task run paths without manual bootstrap.
  4. Runtime-proof scope correctness: proof cleanup and selected checks now stay bound to the selected workflow/task closure, not unrelated execution contexts.
  5. Runtime-proof JSON consistency: non-blocking info findings no longer cause false failed proof outcomes when verdict is ready; JSON now includes failure_class for machine classification.
  6. Service readiness truth in ota up: detached service-run semantics now preserve surface-readiness failures, with clearer bind-conflict diagnostics (including EADDRINUSE tails) and corrected startup classification when a command exits before endpoint readiness.
  7. Mode-aware service proof and runtime/toolchain path reliability: automatic ota up service proof now respects selected mode runtime shape, and native task execution preserves the resolved probe PATH.

This release is about reducing false confidence. Selected path, selected mode, and selected proof surface should always agree.

Docs

Use these docs to apply v1.6.15 patterns directly:

  • Get Started: Install Ota and baseline with ota doctor.
  • Contract reference: Contract for execution modes, task dependencies, and agent boundaries.
  • Command reference: Commands for ota run, ota up, ota doctor, and dry-run verification.
  • Workflow modeling: Workflows for selected-path readiness and execution behavior.

Release

v1.6.15 is live here: https://ota.run/releases/v1.6.15

If you already run Ota, verify quickly:

VERIFYbash
ota --versionota validateota doctorota proof runtime --workflow <workflow-name> --json

If your repo relies on container execution and detached service readiness, this release gives you cleaner mode fidelity, better proof consistency, and more actionable failure output.