Skip to main content

Version compatibility

A Workflow project's devDependencies.steamharness must declare an exact SemVer such as "0.2.7" or "0.2.7-20260826001". This records the development baseline; runtime compatibility compares only major.minor.

0.2.0, 0.2.99, 0.2.4-20260826001 and 0.2.4-beta.1 all belong to 0.2.x. Patch and prerelease ordering do not affect compatibility. A major or minor mismatch stops execution before loading user code and reports the project version, host version and required line.

Breaking Core API changes require a new minor compatibility line rather than a patch release.

Local execution and Server storage​

  • Studio resolves and starts the CLI installed in the project. Project inspection and execution use that CLI's Core; install the declared dependencies and align incompatible lines to a verified combination.
  • CLI binds an exact Core and limits its peer range to the same minor, such as >=0.2.0 <0.3.0. run, json, structure and resolve-params validate the installed Core, CLI binding and project declaration.
  • Server validates static project declarations and stores source snapshots without installing dependencies or executing project code. The local CLI validates runtime compatibility after download.

Built-in project snapshots​

Studio's built-in assistant and Studio Control use repository-pinned project snapshots. Development dependencies can resolve from the assistant repository in the aggregate. Studio Control exposes limited workspace and editor operations through a session-authenticated extension host and standard assistant MCP. Legacy Desktop Control has been removed from the current integration branch.

Existing built-in release indexes retain components.core, components.cli and minDesktopVersion as release metadata. Studio packages, release channels and index integration are configured separately. See Studio workstation for source execution.