Skip to main content

v2.58 (with v2.55 – v2.57)

These notes cover everything landed between v2.54.0 (2026-08-16) and v2.58.15 (2026-09-19), across four minor releases. The headline is that a registered baseline can now be built from the command line, on your machine or on the platform, and that the engine underneath it, the bootstrap engine, can stop, resume, and report itself without a model attached. Start with the guide.

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

v2.58​

Released 2026-09-16; patched through v2.58.15 on 2026-09-19.

orun baseline new --via-platform​

Asks the platform to build a registered baseline into a repository this workspace has linked, in a sandbox the platform provisions, and prints a session id to watch. The repository is resolved and printed before anything starts, and an ambiguous one is refused rather than picked. The admin requirement, the paid gate, readiness, the repository grounding, and the one-build-per-repository lease all live on the server and are reported verbatim. See orun baseline.

orun baseline register and orun baseline publish​

Register a baseline your account owns, and later move it to a new tag. A baseline that declares neither --brief nor --umbrella is blueprint-driven: its build document declares every phase and there is no shell layer to read. publish proves the tag before the registry moves: it must be a tag, the files a build reads first must be in it, and the manifest must parse. The registry's owner/name is a repository, not a hostname (v2.58.1).

The bootstrap driver​

orun agent serve --driver bootstrap supervises a build with no model attached. It is what the platform sandbox runs, and it runs exactly orun baseline new <id>@<tag> --local --run-hooks --resume --progress json. The build reports itself as a stream of bootstrap-event/v1 events the console renders.

Hardening a platform build (v2.58.3 – v2.58.15)​

Twenty patch releases in four days, each one a defect met while making a baseline bootstrap itself. In the order they matter to an operator:

  • A phase says each step as it happens, not only when it is over, and a build says what it is waiting on before it waits.
  • A resumed build says an earlier run placed a phase, instead of "not needed". A grounded console build is placed in its clone, so a Build after a stopped one resumes.
  • A GitHub read that is reset is asked again: one dropped connection no longer ends a build. A console build reaches GitHub through its session, asking the platform's repository token per request.
  • A landing waits for the pull request's CI to finish, not for the checks that happen to exist when it looks. A phase lands only what it placed; the landing commits, converges on its own commit, and can land twice.
  • An input can be filled from the workspace the build runs in (from: workspace). A mistyped input key is refused before the prompts, not after. A project a fresh build has not created yet is "not yet", not a failure.
  • The workspace you named is enough. Hooks read ORUN_WORKSPACE, and the repository link stops being a prerequisite for a local build.
  • orun auth status checks the login still works, and an unreadable credential store stops posing as "not logged in". Tests never touch the developer's keychain.
  • A published secret is looked for where it was published: the project's environments. GitHub is connected only through the account that owns the product's repository. The backend URL chain ends at the production API.
  • Four defects that made a baseline unable to bootstrap itself (v2.58.4).

v2.57.0​

Released 2026-09-15.

orun baseline new --local​

Builds a registered baseline on this machine. The registry says where the baseline lives and which commit is published; its manifest says which document inside that tree is the build; --local clones at the tag, reads the one key it needs, and runs the build document through the same engine as orun new. Joining those facts by hand is work nobody should repeat. --run-hooks is the difference between placing files and bootstrapping a product.

v2.56.0​

Released 2026-09-15.

orun baseline: the registry from the command line​

orun baseline list, show, and check. show prints the source, the time budget, and one row per required provider; check turns readiness into an exit code for a script or a CI gate. Nothing is written and no build starts.

The bootstrap engine​

The Blueprint already had phases, hooks, and placement barriers. This release gave it the verbs, the wait, and the words:

  • A hook can call a typed action (uses:), and a bad parameter is a parse error before anything is placed. The action set is closed at nine: the task plane's task/ensure, the workspace actions for connections, secrets, and reconcile, and the GitHub-side actions. The workflow hook is gone; a hook either runs a command or uses an action.
  • A phase states what must be true before it runs, and a phase can wait without failing when a condition it depends on is not yet met.
  • Phase state is derived, so a fresh container can answer which phases are done. This is what makes --resume safe.
  • The engine reports itself in two registers: a human progress line and a machine event stream (--progress json).
  • The engine's own words: what it will and will not claim about a build, and what drift means to a product that has been branded.
  • The pen can finish a landing, not just start one (orun pr land).
  • A log chunk goes out knowing which step it came from.

v2.55.0​

Released 2026-09-11; patched through v2.55.2.

The task plane grows containers​

orun task epic create|show|list and orun task milestone create give a task a place to belong. orun task create says where the task belongs and attaches a template contract. The same tools reach agents through the MCP, whose platform manifest is re-vendored at 33 tools. See orun task and the task plane.

orun spec push and orun spec list​

Spec docs are repo-authored markdown, annotated to epics, and pushed with their commit. See orun spec.

The pen takes the flow's branch​

orun pr open takes the flow's branch slug, the epic, and a body file, so a baseline build can open its own task-carrying pull requests.

Agent runtime​

The bootstrapper persona defers to the brief's questions and forbids environment repair. The programme tools ride the allow lane, and harness gates apply over the composed roster. orun agent serve seeds ORUN_BACKEND_URL for the harness from the dial-home identity.

Upgrading​

No intent, plan, or object-model format changed in these releases. Install the latest binary and run orun auth status; a session from an older release keeps working, and the new liveness check will tell you if it does not.

curl -fsSL https://raw.githubusercontent.com/sourceplane/orun/main/install.sh | sh
orun version
orun auth status