@unotest/viewer 0.20.0 → 0.22.0

package/CHANGELOG.md

@@ -1,5 +1,99 @@
 # Changelog
 
+## [0.22.0] - 2026-08-26
+
+### Patch Changes
+
+- 80619a9: Run on NestJS 11 and Fastify 5.
+
+  The viewer's server was pinned to `@nestjs/* ^10.4.0`, which held the whole
+  prod tree on an EOL Fastify 4 line: `@fastify/static` 7 (path traversal past
+  a route guard — reachable, the viewer serves its SPA through it),
+  `@fastify/middie` 8 (unreachable here, but flagged forever by scanners),
+  `@nestjs/platform-fastify` 10 (middleware-bypass series) and `ws` 8.18
+  (memory-exhaustion DoS on the viewer's live channel).
+
+  Nest 11 + Fastify 5 retires all of it: `@fastify/middie` leaves the tree
+  entirely, `@fastify/static` moves to 10, `ws` to 8.21. `npm audit
+--omit=dev` on a freshly packed tarball reports zero vulnerabilities.
+
+  No public API change — same server, same endpoints, same `@unotest/viewer`
+  surface.
+
+  - @unotest/dsl@0.22.0
+  - @unotest/protocol@0.22.0
+
+## [0.21.0] - 2026-08-25
+
+### Minor Changes
+
+- 174d27e: feat: environments are first-class in the viewer — a switcher, per-env run history
+
+  **Run artifacts are laid out per environment, as folders.** Each
+  environment's history lives in its own root, mirroring the env-file
+  scheme: `unotest/.runs` (base), `unotest/.runs.<env>` (e.g.
+  `.runs.staging` for `--env staging` / `UNOTEST_ENV=staging`); the axes
+  compose — `.runs-mobile.staging`. Indexes (`_day.jsonl`, `_latest.json`)
+  are per-env automatically: switching environments is a change of root,
+  not a filter and not a rebuild. Old runs stay in `.runs` (= base), no
+  migration needed. `runsDirFor` / `projectRunsRoot` / `projectRunDirFor`
+  gained an optional `envName` parameter; the run manifest carries `env`
+  for self-description. Make sure your `.gitignore` uses the wildcard
+  form — `unotest/.runs*/` (`init` already writes it that way for new
+  projects).
+
+  **The viewer knows about environments.** A new switcher sits at the top
+  of the Variables panel and in the status bar: base plus every
+  environment discovered from `unotest/.env.<name>` / `.secrets.<name>`
+  (`.env.example` and other templates do not count). The active
+  environment is server-side (`GET/POST /api/environments`), and all tabs
+  converge via the `env:changed` WS message:
+
+  - the Variables panel shows layers WITH the active environment's
+    overlay (previously base only); values coming from `.env.<name>`
+    carry a badge; an edit goes to the file where the key is defined; new
+    variables go to base;
+  - Overview and the Runs list show only the active environment — tiles
+    are colored by the latest run in that environment;
+  - a run started from the viewer gets the active environment's
+    `UNOTEST_ENV` (`RunRequest.env` is a per-request override);
+  - a run opened from another environment still resolves by runId across
+    all `.runs*` roots.
+
+  MCP: `run_test {env}` already switched the child process's environment;
+  its artifacts are now correctly found by the server in `.runs.<env>`
+  (inspect/step/attach/list_runtimes scan all roots).
+
+  Four fixes uncovered while shaking this down:
+
+  - **The `--env` overlay actually reaches the run.** Long-lived hosts
+    (viewer, MCP server) flattened the base `.env` into their own
+    `process.env` on `loadConfig`; children inherited it as ambient
+    (ambient beats files) — the overlay's `APP_BASE_URL` was silently
+    clobbered by the base value. The viewer now rolls its env back after
+    loading the config; MCP spawns children from a clean pre-flatten
+    snapshot.
+  - **Pause/Abort from the viewer work again.** Debug commands were
+    written to the flat `<root>/<runId>/commands.jsonl`, while runs have
+    lived in date shards since 0.19 — the write 404'd and abort was
+    silently ignored. Order fixed too: SIGTERM to the own process first
+    (tests AND collections), then the command file.
+  - **A collection no longer "dies" in the UI after 30 seconds.** The
+    parent run wrote no heartbeat — the monitor declared it interrupted,
+    the row vanished from ACTIVE and the tail detached. The orchestrator
+    now maintains the heartbeat (shared machinery in `@unotest/core`),
+    and the viewer additionally treats a flowing steps.jsonl as a sign of
+    life (compatibility with older runners).
+  - **No phantom `failed` after a clean exit.** The "child exited without
+    artifacts" check looked at the flat path and fired bogus
+    `run-finished: failed` events plus an error toast on every exit.
+
+### Patch Changes
+
+- Updated dependencies [174d27e]
+  - @unotest/protocol@0.21.0
+  - @unotest/dsl@0.21.0
+
 ## [0.20.0] - 2026-08-24
 
 ### Minor Changes

package/dist/server/main.d.ts

@@ -23,6 +23,9 @@ interface StartViewerOptions {
     /** Target id selected at boot (`web`/`mobile`/…). Defaults to the first
      *  available runner. */
     activeTarget?: string;
+    /** Environment name selected at boot (M-11 dot axis, `--env` /
+     *  `UNOTEST_ENV` of the launcher). Blank/unset = base. */
+    activeEnv?: string;
     /** Port to bind. `0` = OS picks a free port. Default 0. */
     port?: number;
     /** Host to bind. Default 'localhost' (loopback only). */