RoboVAST 2.2.1

pip install robovast-client              # drive a RoboVAST service someone runs for you
pip install "robovast[nav,roqsim]"       # the core: configuration, results, the MCP server
pip install robovast-cluster             # deploy and run the service on a Kubernetes cluster

Then vast cluster setup deploys the service — into minikube on your own machine, or a cluster for a team. Container images for this version, tagged 2.2.1: ghcr.io/cps-test-lab/robovast and robovast-roqsim for linux/amd64 and linux/arm64, and robovast-controller and robovast-sidecar, which run only in the cluster, for linux/amd64.

What changed

• Pinned simulator — the roqsim image builds the roqsim commit its Dockerfile pins, the last this line supports
  (#900)
• MCP image tag — start_campaign takes image_project_tag, as the CLI's --image-project-tag does
  (#709)
• Screenshots kept — a simulation screenshot is stored and addressable by path, not only returned inline
  (#708)
• World check — the project check reports what the simulator warns about a world's start state
  (#715)
• Exit codes — vast campaign wait and vast image wait define their codes once; help, docs and MCP render that list
  (#719)
• Admission — a pass is linear in the queue, sizes a queued job once per node, and reads the cluster outside its lock
  (#699, #881)
• Free disk — admission takes a node's free disk as the kubelet measures it, less its eviction threshold
  (#892)
• Postprocessing — a failed conversion delivers what it converted; an OOM-killed stage step fails its pod instead of holding it
  (#880, #899)
• Stall report — a campaign whose batch has finished every run is not called queued
  (#707)
• Archived campaigns — read as archived on the exec path too, so a key they ran without does not refuse them
  (#692)
• roqsim socket — a ros-shape run names its control socket on /ipc for simulator and scenario alike
  (#894)
• roqsim image — no longer installs roqsim_webctrl, which roqsim does not ship
  (#898)

RoboVAST 2.2.0

pip install robovast-client              # drive a RoboVAST service someone runs for you
pip install "robovast[nav,roqsim]"       # the core: configuration, results, the MCP server
pip install robovast-cluster             # deploy and run the service on a Kubernetes cluster

Then vast cluster setup deploys the service — into minikube on your own machine, or a cluster for a team. Container images for this version, tagged 2.2.0: ghcr.io/cps-test-lab/robovast and robovast-roqsim for linux/amd64 and linux/arm64, and robovast-controller and robovast-sidecar, which run only in the cluster, for linux/amd64.

What changed

• Local Docker lane removed — campaigns run on a Kubernetes cluster, on one machine a minikube or kind; vast serve needs robovast-cluster
  (#675)
• Settings refused — a .vast that sets execution.local or show_gui is refused, since nothing reads them
  (#675)
• Navigation MCP tools retired — core answers them for any robot: pose_track_view, get_track_deviation, get_config_contribution, draw_config
  (#640)
• Pinned deployments — the admin page offers Upgrade only on a tag CI moves; move a pinned version with vast service upgrade
  (#691)
• Workspace archives — download, share and re-create a workspace as one archive
  (#657)
• Simulator docs from the image — a simulator's documentation and spawnable components are read from the image that runs them
  (#521, #526, #683)
• Campaign management — delete several campaigns at once, and sort the list by recency or size
  (#648, #646)
• Stopping — a stop takes effect in every wait, and a campaign's auxiliary containers end with it
  (#616, #618)
• Parallel postprocessing — a campaign's postprocessing is split across Jobs, per run where a plugin allows it
  (#601)
• Simulator provenance — a campaign records which simulator commit it ran, and flags images built from different ones
  (#660)
• Run view — a Run-view button on the campaign card, and the costmap panel drawn onto a rendered video
  (#643, #578)
• TurtleBot 4 in the images — the roqsim image carries the Create 3 / TurtleBot 4 stack
  (#633, #664)

RoboVAST 2.1.0

The first release of the 2.x line, and the first in which every documented install resolves from PyPI. RoboVAST now ships as five distributions released together at one version:

robovast-client	the vast CLI and everything that only drives a service — ~30 MB, no simulator, no Docker, no Kubernetes client
robovast	the service: configuration and variation, the campaign controller, results and the Postgres-backed index, the MCP server, the web UI, the local Docker lane
robovast-nav	navigation variation types (floorplans, paths, obstacles) and their web panels
robovast-sim-roqsim	the backend: roqsim simulator backend, as the roqsim extra
robovast-cluster	the Kubernetes execution lane and the operator verbs of vast cluster

pip install robovast-client              # drive a deployed service
pip install "robovast[nav,roqsim]"       # run one locally, with Docker
pip install robovast-cluster             # add the Kubernetes lane

The robovast and robovast-nav wheels carry their built frontends, so an installed service serves the web UI and the navigation panels without a checkout.

Container images for the same version: ghcr.io/cps-test-lab/robovast:2.1.0 and the family it belongs to, for linux/amd64 and linux/arm64.

Since 1.0.0: the client split, campaigns indexed in Postgres, the roqsim backend and the cluster lane as their own distributions, the agent interface (MCP) and the web UI as first-class clients, and the campaign controller as its own image. Documentation: https://cps-test-lab.github.io/robovast/