Skip to main content

TestVibe 0.4.9

All release notes · Self-hosted upgrade guide

Archived release. Superseded by newer releases; downloads are no longer offered.

The appliance administration console stays up. Its systemd unit declared Type=notify on a process that never sends the readiness signal, so systemd killed a console that was already serving and restarted it roughly every 96 seconds — and since console session state is in-process, every kill was a silent sign-out, usually mid-setup-checklist. Container and Kubernetes installs were never affected. All four artifacts are published: containers, Helm chart, VHDX and OVA.

  • The console stops restarting, and the appliance build now refuses to produce an image if any TestVibe unit declares Type=notify — the defect was a one-word mismatch no check on a running box would surface, so the gate belongs at build time.
  • The console honours sessionTimeout and autoReload: an expired console session reloads itself instead of leaving a dead page.
  • A Jira story or a GitHub issue can now carry its own test evidence. Point the loop at a story and TestVibe drafts the test features it implies; a human presses Generate to approve; the tests generate and run; and the outcome is reported back on the original story as one comment edited in place through generate, run and verdict — not four comments nobody reads.
  • The issue composer gains an optional Generate button that turns the deterministic transcript into an AI analysis before you file — body-only, non-fatal when the model is unavailable, and deliberately unreachable from the create_issue automation action (an automation must not silently spend AI credit).
  • An issue filed from a run that passed is no longer labelled test-failure — the label follows the actual outcome, for generations too.

Upgrading: Docker — take this release's docker-compose.yml first, then pull and docker compose up -d. Kubernetes — helm upgrade to chart 0.4.9, passing the same secrets you installed with. Appliance — replace the OS disk with the 0.4.9 one and keep your data disk.

Schema migrations: one (V0277 — the story test loop's table and a nullable tv_feature.issue_loop_id). Structure only; nothing is backfilled. Upgrading from 0.4.7 applies the same single migration — 0.4.8 shipped no schema change.