Skip to main content

v2.95.0

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

This release is part of orun-cloud's saas-parallel-baselining PB2: the first change of an app's plan starts from the commit its baseline merged, while the baseline carries on deploying.

The merge commit, on the pr fact​

A blueprint build reports the pull request each landing opens as a pr fact (orun.pr/land@v1): #number, its URL and where it stands (opening, checks, failing, open, merged, closed). Once it is merged, the fact now also carries the commit it landed as, sha on the wire:

{ "state": "fact", "phase": "01-product", "step": "land",
  "meta": { "fact": "1", "kind": "pr", "value": "#1", "href": "https://github.com/acme/notes/pull/1",
            "status": "merged", "sha": "3f2a9c1d…" } }

A reader that follows a build — orun.work, through the platform's build events — knows the moment the code is on the base branch, and where, without waiting for the build to finish. Before it is merged the fact has no sha. It was already a hook output (.hooks.<id>.outputs.mergeSha); now it reaches the build stream too.