Skip to content

v1.9.0.md

Latest commit

 

History

History
74 lines (53 loc) · 4.48 KB

v1.9.0.md

File metadata and controls

74 lines (53 loc) · 4.48 KB
Raw

Viaduct v1.9.0 Release Notes

Published 2026-04-11.

Viaduct v1.9.0 turns the refreshed dashboard and packaged web assets into a cleaner startup path. This release does not add a second UI stack or change the backend architecture. Instead, it closes the gap between the documented install story and the shipped artifacts by making the built dashboard available directly from viaduct serve-api, tightening deployment examples, and synchronizing the docs, packaging, and release surfaces around the same behavior.

Highlights

  • viaduct serve-api now serves built dashboard assets automatically when they are present in web/dist, a packaged web/ directory, or an installed share/viaduct/web layout.
  • The default first-run and lab guidance now lead with one same-origin dashboard path at http://localhost:8080.
  • Container and deployment examples now invoke the shipped image correctly instead of appending conflicting command arguments to the existing entrypoint.
  • Package, install, upgrade, troubleshooting, and demo surfaces now describe the same dashboard, CLI, and API behavior.

Dashboard Startup

  • The local source workflow now builds both the CLI and dashboard, starts viaduct serve-api, and opens the operator shell at /.
  • Packaged installs and extracted release bundles use the same startup command and the same root URL.
  • The Vite development server remains documented for frontend development, but it is no longer the default dashboard path.
  • When the dashboard is served from the same origin as the API, no extra CORS configuration is required.

Packaging And Deployment

  • Added a --web-dir flag and VIADUCT_WEB_DIR environment variable for non-standard dashboard asset locations.
  • Standardized the installed dashboard asset path on Windows to match the existing Unix-like layout.
  • Updated the container image to use ENTRYPOINT ["viaduct"] and CMD ["serve-api", "--port", "8080"] so Compose and Kubernetes overrides behave predictably.
  • Corrected the Compose and Kubernetes references so they expose the intended dashboard-plus-API listener.

Docs And Release Surfaces

  • Updated the root README, install guide, quickstarts, assessment guide, deployment references, troubleshooting guidance, and configuration reference for the same packaged behavior.
  • Refreshed the demo README and release-facing bootstrap screenshot label for v1.9.0.
  • Kept the local examples/lab workflow as the default reproducible first-run and smoke path.

Screenshot assets:

Compatibility Notes

  • No backend architecture change was introduced in this release.
  • The Go backend, REST API, CLI, React dashboard in web/, and static public site in site/ all remain in place.
  • PostgreSQL remains the recommended durable backend for any persistent environment.
  • examples/lab remains the default first-run and demo path.

Upgrade Steps

  1. Pull the v1.9.0 bundle or checkout the v1.9.0 tag.
  2. Redeploy the binary and matching built dashboard assets together.
  3. If you serve the dashboard from a different browser origin, confirm VIADUCT_ALLOWED_ORIGINS is still set correctly before restart.
  4. If you keep dashboard assets outside the packaged or installed defaults, set VIADUCT_WEB_DIR explicitly before restart.
  5. Rerun the lab or supervised pilot smoke path to confirm authentication, workspace progression, and report export.

Verification

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

Known Issues

  • The dashboard still depends on backend-persisted state; it does not replace connector configuration or migration execution surfaces that remain CLI or API driven.
  • Higher-risk migration execution outside the documented lab or supervised pilot flow should still be validated in a controlled environment first.

Rollback Notes

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