Skip to Content
Releases0.1.x Beta

OpenSoha 0.1.x Releases

OpenSoha components use independent semantic versions. A release set records compatible public artifacts; it does not require every repository, runtime image, npm package, or Helm chart to share one version number.

Core, Web, Contracts, CLI, Agent, Skills, and Connectors are published from opensoha/soha under component-scoped tags, while opensoha/soha-operator and opensoha/soha-helm maintain independent repositories and release cycles.

November 2026 Consolidated Release Set

ComponentVersion / TagPublic artifact
Contractscontracts/v0.2.0@opensoha/contracts@0.2.0, Go module github.com/opensoha/soha/contracts@v0.2.0, and GitHub Release 
Soha control plane (embedded Web)v0.1.13GitHub Release  assets are soha-linux-amd64, soha-linux-amd64.sha256, and soha-release-manifest.json; Web is embedded in the binary and ghcr.io/opensoha/soha:v0.1.13, with matching soha-network-gateway, soha-proxy-mihomo, soha-proxy-sing-box, soha-proxy-v2ray, and soha-radius images
Soha CLIcli/v0.2.1GitHub Release , @opensoha/cli@0.2.1, Go module github.com/opensoha/soha/cli@v0.2.1, and ghcr.io/opensoha/soha-cli:v0.2.1
Soha Agent and runtimesagent/v0.2.0GitHub Release , ghcr.io/opensoha/soha-agent:v0.2.0, ghcr.io/opensoha/soha-dsh:v0.2.0, ghcr.io/opensoha/soha-docker-volume-reader:v0.2.0, ghcr.io/opensoha/soha-buildpacks-agent:v0.2.0, and ghcr.io/opensoha/soha-buildpacks-agent:daemonless-v0.2.0
Soha Operatorv0.1.1GitHub Release  and ghcr.io/opensoha/soha-operator:0.1.1 (also tagged v0.1.1)
Official skillsskills/v0.1.4GitHub Release  validated package and signatures
Official connectorsconnectors/v0.1.1GitHub Release  validated runtime packages and manifests

The public Helm repository is https://opensoha.github.io/soha-helm. Currently published chart versions are:

Helm chartPublished chart versionDefault runtime appVersionStatus
soha0.1.100.1.9Chart update targeting Core v0.1.13 is pending publication
soha-agent0.2.50.1.9Chart update targeting Agent v0.2.0 is pending publication
soha-hermes-agent0.1.70.1.7New Hermes images stopped after v0.1.12; existing images remain available
soha-operator0.1.20.1.1Matches Operator v0.1.1
soha-observability0.2.10.157.0Preserves logs-only default with optional authenticated OTLP metrics and traces

Highlights

  • Consolidated Root publishing: the six former standalone component repositories (soha-contracts, soha-web, soha-cli, soha-agent, soha-skills, soha-connectors) are now archived read-only historical sources. Component releases publish from opensoha/soha, and Core embeds the Web console built from the same release commit.
  • Contracts 0.2.0: establishes the github.com/opensoha/soha/contracts Go module path and @opensoha/contracts@0.2.0 npm package, including agent/dsh-runtime.schema.json, workspace and VM schemas, and governed CLI session endpoints.
  • Core v0.1.13 and Agent v0.2.0: ship unified intranet-access runtime images, opt-in dsh / Hindsight configuration (disabled by default), and multi-architecture soha-dsh:v0.2.0, soha-docker-volume-reader:v0.2.0, and soha-buildpacks-agent images. Hermes runner stopped publishing new images while preserving existing images and optional Compose runner support.
  • CLI v0.2.1: fixes npm 12 pack-descriptor verification and completes public qualification for the signed npm launcher, native archives, Go submodule, and multi-architecture container image (cli/v0.2.0 published native archives and container image only, without an npm package; its immutable artifacts remain intact).
  • Operator v0.1.1: updates WorkloadCronJob reconciliation and source/CronJob resourceVersion status tracking, paired with soha-operator Helm chart 0.1.2.

Upgrade Order

  1. Upgrade downstream components and external consumers only after both the @opensoha/contracts npm package and the github.com/opensoha/soha/contracts Go module tag resolve.
  2. Core v0.1.13 already embeds the verified same-commit Web console build. Before enabling new Chat or Heya traffic, deploy the matching soha-dsh:v0.2.0 image and complete the offline cutover described in Agent Runtime.
  3. Upgrade Agent, CLI, and Operator independently. Their compatibility boundary is the public API, Agent protocol, and capability matrix rather than matching SemVer numbers.
  4. Upgrade Helm charts after their referenced GHCR images are available. Chart versions and appVersion follow separate version sequences; until updated soha and soha-agent charts are published, do not assume chart defaults point to v0.1.13 or v0.2.0.

Soha, CLI, Agent, DSH, and network runtime images use v-prefixed runtime tags. Operator publishes both vX.Y.Z and unprefixed X.Y.Z tags; native manifests and the Operator Helm chart derive 0.1.1 from appVersion.

Rollback

  • Roll back Soha together with its matching Core image (including the embedded Web build), network runtime images, and database compatibility window; retain active credential encryption keys whenever encrypted checkpoints exist.
  • Roll back Agent, DSH, Hermes, or Operator by pinning the previous verified image and matching manifest or chart version together.
  • Published npm packages, Go module tags, and GHCR release tags are immutable. Ship a forward patch (such as cli/v0.2.1) rather than moving tags or overwriting public artifacts.

Verification And Historical Archive Note

soha-web-dist.tar.gz and the Web digest are Actions build artifacts from the release workflow, not standalone GitHub Release downloads for v0.1.13. The public manifest records the same-commit Web digest; the released binary and image already include the console.

Release workflows verify exact commit bindings, checksums, cryptographic provenance, and re-downloaded public assets. Core, Agent, CLI, and Operator primary runtime images publish multi-architecture GHCR manifests (soha-proxy-v2ray and soha-radius currently target linux/amd64).

Original tags and release bytes from the August 2026 release set (Contracts 0.1.13, Core / Web / CLI / Agent v0.1.6, Operator v0.1.0, Skills v0.1.1) are preserved in the Root historical archive. Because the six former standalone component repositories are archived and retired from active development, legacy repository URLs and old Go module paths may stop resolving; pin new installations to the opensoha/soha and opensoha/soha-operator artifacts listed above.

Last updated on