Skip to main content

v2.82.0

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

The repository is not a work tracker​

From v2.64.0 to v2.81.1 a repository could declare its work: an epic.yaml per epic under the directory intent.yaml named in work.epics, task contracts under work.tasks, orun work check to judge the tree before a merge and, with work.sync: on-merge, the orun plan on the default branch reconciling the tree into Orunbase after a successful plan and locking every declared epic as managed (orun-cloud saas-work-gitops). Orunbase has removed that model (saas-work-gitops-teardown): an epic is a Linear project mirrored in, or an epic created in Orunbase, and nothing a file declares owns one. orun follows.

  • orun work is gone — both check and sync.
  • orun plan runs no work sync. The plan's exit code, its output and the catalog auto-publish are exactly as before.
  • work: in intent.yaml means nothing. A repository that still carries the section loads and plans as before; orun plan prints one notice naming it, and removing the section silences the notice. work.tasks no longer moves the contracts directory: orun task attach, orun task check, orun task create --contract and orun pr check read tasks/<KEY>.TaskContract.yaml at the repository root, as they did before v2.64.0.
  • The platform client no longer sends the X-Orun-Work-Sync header and no longer carries an epic's managedBy pointer or a keyPrefix; orun task epic, orun task milestone and orun task are unchanged.
  • The software-factory skill mints an epic where the workspace creates work — over MCP, or in the tracker — and lands its doc set as the first pull request; its epic.yaml template is gone.

What stays: orun task (epics, milestones, tasks, contracts), orun spec push, orun pr (the provenance pen), orun githooks, and the task contract in tasks/.