Skip to main content

v2.73.2

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

This release is the third milestone (PD3) of the documentation epic that re-frames orun as platform discipline as code. It covers pillar 2, package and evolve: standards that travel and change like code.

One path for standards that travel​

The pillar now reads in order, each page linking the next: compositions → Stacks → intent presets → versioning and locking → baselines.

  • Intent presets is rewritten as the pillar's flagship: how a platform team ships its platform rules inside a Stack and every repository inherits them with extends:.
  • Versioning and locking is new. It covers what carries a version, the two strengths of pin (a version tag, or a digest: that orun plan enforces), what every plan records, how to review an upgrade, and how orun new upgrade three-way merges a newer blueprint into a product.
  • Stacks, baselines, and writing compositions open with what each does for a standard; baselines are "a whole product's structure and standards, packaged".

Corrections​

  • Preset precedence was backwards. Presets fill in what the repository leaves out, in extends: order, so the repository always wins and the first preset to set a value wins, not the last. policies are the exception: a preset's keys overwrite the repository's. The merge table now lists exactly what is merged for each field; promotion, dependencyMode, and secretEnv are never merged into an existing environment.
  • orun validate does not apply presets; run orun plan to check the effective intent.
  • The repository-scale output gate of orun new and orun baseline new runs orun validate and a full orun plan compile. It was described as orun plan --dry-run, which is not a flag.
  • orun compositions lock records resolved digests; it does not pin. The pin is a source digest:.

CLI​

  • orun pack --help and orun publish --help describe a Stack (stack.yaml, or the legacy orun.yaml). pack previously named only orun.yaml.