Skip to main content

v2.75.0

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

orun run <id> runs the plan you just made​

orun plan ends by suggesting orun run <id>. That id is the plan's short checksum, but revisions were looked up only by the hash they are stored under, so the suggestion failed with no component matched. A plan reference now resolves by either: the id orun plan prints, or a prefix of the stored hash, with or without its sha256- prefix.

orun plan reads at a glance​

The summary leads with the shape of the plan:

✓ Plan da6acc29f1de  ·  2 components × 2 envs → 4 jobs

  staging
  ├─ api  verify   test → build
  └─ web  verify   test → build            after api
  production                               after staging
  ├─ api  release  test → build → package
  └─ web  release  test → build → package  after api

  revision  rev-manual-…
  trigger   manual · …

  → orun run da6acc29f1de

On a terminal, plans of up to 24 jobs are listed environment by environment: each job's profile, its steps, and what it waits on. Larger plans and piped output keep the compact form; --view dag is unchanged.

orun new ends in a summary​

By default, orun new now reports what it did in a few lines: the files placed and the phases that placed them, whether the new repository's intent plans (components × environments → jobs), where the provenance lock is, and the next command. The repository check's own output appears only when it fails. --progress verbose (and json) keep the full per-file report.

Quieter output​

  • orun run no longer repeats the runner's result in a second block; it adds the plan revision under the runner's status and logs lines.
  • The object-model: and object-runner: diagnostic lines print only with --debug or ORUN_DEBUG set.

A new README recording​

The README's recording now shows the core loop end to end: build a product from a baseline with orun new, cd into it, orun plan, and orun run. The commands and output are real; scripts/demo/ rebuilds it.