Skip to content

Viaduct v2.0.0

Choose a tag to compare

View all tags
@eblackrps eblackrps released this 11 Apr 23:58
· 151 commits to main since this release
v2.0.0
ed34cf8

Viaduct v2.0.0 Release Notes

Published 2026-04-11.

Viaduct v2.0.0 turns the refreshed dashboard and packaged assets into a cleaner product entrypoint instead of a collection of lower-level setup steps. This release keeps the existing backend, API, CLI, dashboard, and static site in place, but makes installation, startup, first run, and release-facing guidance feel like one coherent operator product.

Highlights

  • Added viaduct start, viaduct stop, and viaduct doctor for the default local operator experience.
  • Made the WebUI-first local path work without manual browser-key seeding by using the built-in local single-user fallback when the default tenant is unkeyed.
  • Updated the install scripts to copy the full packaged surface and generate a starter config that points at the shipped lab fixtures.
  • Synchronized the dashboard, docs, screenshots, release notes, and public site around the same startup and workspace-first flow.

Installation And Startup

  • viaduct start now serves the API and bundled dashboard together for the standard local path.
  • On a fresh source checkout, viaduct start creates ~/.viaduct/config.yaml automatically when it is missing and points it at examples/lab/kvm.
  • viaduct stop shuts down the recorded local runtime cleanly.
  • viaduct doctor validates the local config path, bundled dashboard assets, lab fixtures, and runtime reachability.
  • viaduct status --runtime reports the recorded local runtime, including the WebUI URL, API URL, PID, mode, and log path.

WebUI-First Operator Flow

  • The default local URL is now http://127.0.0.1:8080.
  • The dashboard remains workspace-first: create workspace, discover, inspect, simulate, save plan, and export report.
  • Tenant keys and service-account keys are still supported, but the default local lab flow no longer requires pasted credentials.
  • Runtime browser storage still defaults to the current session, with an explicit remember option for trusted workstations when keys are used.

Packaging And Deployment

  • The Unix and Windows install scripts now copy docs, examples, configs, and built web assets together.
  • Installers generate a starter config for the installed lab path when no config already exists at the target location.
  • Container, Compose, systemd, and Kubernetes guidance now clearly distinguish the local start path from the lower-level serve-api service path.
  • The packaged dashboard, CLI, API, docs, and examples continue to ship together in the release bundles.

Connector And Compatibility Notes

  • Built-in connector coverage remains: VMware, Proxmox, Hyper-V, KVM, Nutanix, and Veeam, plus the gRPC plugin host for community extensions.
  • Fixture-backed certification remains explicit for KVM and Proxmox through make certification-test.
  • Plugin manifest compatibility remains validated through make plugin-check.
  • PostgreSQL remains the recommended persistent backend outside the default local lab path.

Upgrade Notes

  1. Pull the v2.0.0 bundle or checkout the v2.0.0 tag.
  2. Redeploy the Viaduct binary and the matching built dashboard assets together.
  3. If you use packaged installs, rerun the updated installer so the starter config, examples, and docs land in the expected layout.
  4. Prefer viaduct start for the local operator path and keep viaduct serve-api for service, container, or intentionally headless deployments.
  5. If you serve the dashboard from another origin, confirm VIADUCT_ALLOWED_ORIGINS is still correct before restart.

Verification

  • cd web && npm ci && npm run build
  • make release-gate
  • make certification-test
  • make plugin-check
  • make contract-check
  • make package-release-matrix
  • extracted-bundle smoke with viaduct start, viaduct version, viaduct --help, API health, and dashboard root load

Known Notes

  • The default local lab path uses the built-in single-user fallback only when the default tenant is unkeyed and no custom tenants are active.
  • Shared or persistent environments should still use explicit tenant and service-account credentials.
  • viaduct serve-api remains available and documented for service and container contexts; viaduct start is the default local entrypoint, not a replacement for every deployment model.

Rollback Notes

  • v1.9.0 remains the immediate rollback target for this release.
  • Roll back by redeploying the previous binary and matching dashboard assets together, then rerunning the local lab or pilot smoke path.
  • This release does not introduce a documented store migration.
Assets 4
Loading