|
| 1 | +# Viaduct v1.9.0 Release Notes |
| 2 | + |
| 3 | +Published 2026-04-11. |
| 4 | + |
| 5 | +Viaduct v1.9.0 turns the refreshed dashboard and packaged web assets into a cleaner operator-first 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. |
| 6 | + |
| 7 | +## Highlights |
| 8 | + |
| 9 | +- `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. |
| 10 | +- The default first-run and lab guidance now lead with one same-origin operator path at `http://localhost:8080`. |
| 11 | +- Container and deployment examples now invoke the shipped image correctly instead of appending conflicting command arguments to the existing entrypoint. |
| 12 | +- Package, install, upgrade, troubleshooting, and demo surfaces now describe the same dashboard, CLI, and API behavior. |
| 13 | + |
| 14 | +## WebUI-First Startup |
| 15 | + |
| 16 | +- The local source workflow now builds both the CLI and dashboard, starts `viaduct serve-api`, and opens the operator shell at `/`. |
| 17 | +- Packaged installs and extracted release bundles use the same startup command and the same root URL. |
| 18 | +- The Vite development server remains documented for frontend development, but it is no longer the default operator path. |
| 19 | +- When the dashboard is served from the same origin as the API, no extra CORS configuration is required. |
| 20 | + |
| 21 | +## Packaging And Deployment |
| 22 | + |
| 23 | +- Added a `--web-dir` flag and `VIADUCT_WEB_DIR` environment variable for non-standard dashboard asset locations. |
| 24 | +- Standardized the installed dashboard asset path on Windows to match the existing Unix-like layout. |
| 25 | +- Updated the container image to use `ENTRYPOINT ["viaduct"]` and `CMD ["serve-api", "--port", "8080"]` so Compose and Kubernetes overrides behave predictably. |
| 26 | +- Corrected the Compose and Kubernetes references so they expose the intended dashboard-plus-API listener. |
| 27 | + |
| 28 | +## Docs And Release Surfaces |
| 29 | + |
| 30 | +- Updated the root README, install guide, quickstarts, pilot workspace guide, deployment references, troubleshooting guidance, and configuration reference for the same packaged behavior. |
| 31 | +- Refreshed the demo README and release-facing bootstrap screenshot label for `v1.9.0`. |
| 32 | +- Kept the local `examples/lab` workflow as the default reproducible first-run and smoke path. |
| 33 | + |
| 34 | +Screenshot assets: |
| 35 | +- [Pilot bootstrap](../operations/demo/screenshots/pilot-bootstrap.svg) |
| 36 | +- [Pilot workspace flow](../operations/demo/screenshots/pilot-workspace-flow.svg) |
| 37 | +- [Lab workspace flow](../../examples/lab/screenshots/lab-workspace-flow.svg) |
| 38 | +- [Lab report export](../../examples/lab/screenshots/lab-report-export.svg) |
| 39 | + |
| 40 | +## Compatibility Notes |
| 41 | + |
| 42 | +- No backend architecture change was introduced in this release. |
| 43 | +- The Go backend, REST API, CLI, React dashboard in `web/`, and static public site in `site/` all remain in place. |
| 44 | +- PostgreSQL remains the recommended durable backend for any persistent environment. |
| 45 | +- `examples/lab` remains the default first-run and demo path. |
| 46 | + |
| 47 | +## Upgrade Steps |
| 48 | + |
| 49 | +1. Pull the `v1.9.0` bundle or checkout the `v1.9.0` tag. |
| 50 | +2. Redeploy the binary and matching built dashboard assets together. |
| 51 | +3. If you serve the dashboard from a different browser origin, confirm `VIADUCT_ALLOWED_ORIGINS` is still set correctly before restart. |
| 52 | +4. If you keep dashboard assets outside the packaged or installed defaults, set `VIADUCT_WEB_DIR` explicitly before restart. |
| 53 | +5. Rerun the lab or supervised pilot smoke path to confirm authentication, workspace progression, and report export. |
| 54 | + |
| 55 | +## Verification |
| 56 | + |
| 57 | +- `cd web && npm ci && npm run build` |
| 58 | +- `make release-gate` |
| 59 | +- `make certification-test` |
| 60 | +- `make plugin-check` |
| 61 | +- `make contract-check` |
| 62 | +- `make package-release-matrix` |
| 63 | +- packaged bundle smoke with `viaduct version`, `viaduct --help`, API health, and dashboard root load |
| 64 | + |
| 65 | +## Known Issues |
| 66 | + |
| 67 | +- The dashboard still depends on backend-persisted state; it does not replace connector configuration or migration execution surfaces that remain CLI or API driven. |
| 68 | +- Higher-risk migration execution outside the documented lab or supervised pilot flow should still be validated in a controlled environment first. |
| 69 | + |
| 70 | +## Rollback Notes |
| 71 | + |
| 72 | +- `v1.8.0` remains the immediate rollback target for this release. |
| 73 | +- Roll back by redeploying the previous binary and matching dashboard assets together, then rerunning the lab or pilot smoke path. |
| 74 | +- This release does not introduce a documented store migration. |
0 commit comments