Skip to content

v1.7.0.md

Latest commit

 

History

History
87 lines (61 loc) · 5.22 KB

v1.7.0.md

File metadata and controls

87 lines (61 loc) · 5.22 KB
Raw

Viaduct v1.7.0 Release Notes

Published 2026-04-11.

Viaduct v1.7.0 hardens the assessment workflow introduced in v1.6.0. This release improves request validation, viewer permissions, persisted job recovery, dashboard credential handling, and locked-down workstation release verification without widening the product story beyond the current assessment and supervised pilot focus.

Highlights

  • Added stricter validation for assessment create, update, job, and report export requests so invalid input fails early with field-level API errors.
  • Added viewer-safe read and export access while keeping assessment mutation, deletion, and background job execution operator-scoped.
  • Added saved assessment deletion, queued-job recovery on API startup, configurable assessment job timeouts, and richer report details.
  • Switched dashboard runtime auth to session-scoped storage by default with an explicit remember option for trusted workstations.
  • Hardened the Windows release-gate path so make release-gate stays reproducible on workstations that block freshly staged unsigned executables.

Workflow Improvements

The assessment workflow is still:

  1. Sign in with a service account key or tenant key.
  2. Create an assessment.
  3. Run discovery and persist source snapshots.
  4. Inspect workloads and dependency graph state.
  5. Run readiness simulation.
  6. Save a dry-run migration plan.
  7. Export an assessment report.

What changed in this release is the reliability around that path:

  • invalid assessment or job payloads now fail with field-level API guidance instead of generic errors
  • assessment jobs can be retried from saved history in the dashboard
  • queued and in-flight jobs are recovered cleanly when the API restarts
  • exported reports include richer job, approval, note, and report history for troubleshooting

API And Security

  • Added DELETE /api/v1/workspaces/{workspaceID} for tenant-scoped workspace cleanup.
  • Added VIADUCT_ALLOWED_ORIGINS so the API can explicitly allow non-default dashboard origins.
  • Added VIADUCT_WORKSPACE_JOB_TIMEOUT so long-running workspace jobs stay bounded.
  • Tightened browser-facing API responses with explicit origin allowlisting and stronger default security headers.
  • Added an alternate-permission middleware path so viewer-safe routes can stay readable without broadening write access.

Dashboard And Auth

  • Runtime dashboard credentials now stay in session storage by default.
  • Trusted operators can opt into remembered local storage explicitly.
  • Authentication failures now surface a clearer recovery path, including an explicit forget-saved-key action.
  • Assessment history now shows saved jobs, retry actions, and linked request and job IDs.

Release Verification

  • make release-gate remains the release check command.
  • The Windows helper scripts now stage test and smoke binaries under repo-local paths so release validation remains usable on Application Control-constrained workstations.
  • The default examples/lab flow remains the reproducible demo and evaluation path for this release.

Docs And Assets

  • Updated quickstart, installation, troubleshooting, configuration, lab, and assessment docs for the hardened auth and assessment behavior.
  • Updated the OpenAPI contract to include the workspace delete route and current request/response behavior.
  • Refreshed the release-facing screenshot assets and current-version website/dashboard copy.

Screenshot assets:

Compatibility Notes

  • No breaking API removals were introduced in this release.
  • PostgreSQL remains the recommended non-demo backend for persistent operator state.
  • Viaduct remains ready for technical assessment and is still best validated in a local lab or supervised pilot before higher-risk use.

Upgrade Steps

  1. Pull the v1.7.0 bundle or checkout the v1.7.0 tag.
  2. If the dashboard is served from a non-default browser origin, set VIADUCT_ALLOWED_ORIGINS before restarting the API.
  3. If your pilot environment needs longer-running workspace jobs, review VIADUCT_WORKSPACE_JOB_TIMEOUT before promoting the new build.
  4. Prefer service account sign-in for normal users, then rerun the examples/lab assessment-to-report workflow or your supervised pilot smoke path.

Known Issues

  • On some locked-down Windows workstations, Application Control may still block direct execution of freshly staged unsigned test binaries. The release-gate helpers now reroute or fall back when that happens, but operators should still expect the validation logs to call out those fallbacks explicitly.
  • Runtime dashboard keys default to session storage. Operators who choose the remember option should clear saved keys on shared or temporary workstations.

Rollback Notes

  • v1.6.0 remains the immediate rollback target if the workspace hardening changes cause regressions in your pilot environment.
  • Rollback means redeploying the previous CLI, API, and dashboard artifacts together, then rerunning the lab or pilot smoke flow to confirm auth bootstrap, workspace jobs, and report export behavior.
  • This release does not introduce a documented store migration, so rollback is operational rather than schema-driven.