Skip to main content

v2.73.4

Binaries and the merged-pull-request list are on the GitHub releases page.

This release is the fifth milestone (PD5) of the documentation epic that re-frames orun as platform discipline as code. It covers pillar 4, verify, plan, execute: the runner that checks the intent, compiles a deterministic plan, runs it anywhere, and records what happened.

The runner, in order​

  • How orun works is the runner's walkthrough: declare, verify (orun validate), plan, execute, record. The compiler table now says where each check happens: source pins and presets at load, component schemas after normalisation, secret references at expand.
  • The quick start follows the four pillars, adds a step that shows what an agent sees (orun agent context, orun mcp tools), and every command in it was run against this release.
  • Verify a pull request is a new guide to the checks to run on every pull request: validate, the blast radius, the changed plan, and the task contract.
  • Distributed execution with remote state is rewritten for Orunbase. A backend URL is optional; orun resolves it from the flag, ORUN_BACKEND_URL, intent.yaml, ~/.orun/config.yaml, and finally Orunbase's API.
  • orun run init is documented.

Change detection: selection versus blast radius​

Change detection now absorbs the change watches page and states the rule the code follows. --changed plans the directly changed components, their build-input dependents (dependsOn with input: true), and dependencies pulled in with include: always. Ordinary dependents are in the blast radius (orun catalog affected) but are not planned. The old change watches page said they were; it now points to the corrected section.

Corrections​

  • Runs resume by running again with the same --exec-id; there is no orun run --resume. Execution state lives in the object model under .orun/objectmodel/, not .orun/runs/ (runners, cockpit).
  • Plans are no longer written to .orun/plans/. A positional argument to orun run resolves latest, a revision key, or a checksum prefix; a name given to orun plan --name is not a run reference.
  • The quick start no longer says orun validate checks component schemas or that orun compositions lock pins sources.
  • Plans carry no timestamp (plan DAG page).

CLI​

  • orun plan --help describes --output (an extra copy; every plan is sealed into the object model) and --name (a display name) accurately.