Skip to main content

TestVibe 0.4.2

All release notes · Self-hosted upgrade guide

Archived release. Superseded by 0.4.3. Downloads are no longer offered; these notes remain available for upgrade planning.

An appliance-only release, and a security fix. There were no 0.4.2 containers or Helm chart.

Every copy of the 0.4.0 and 0.4.1 appliance images shipped with identical secrets — the same secret-protection key, database password, blob and runner keys, administrator password and install identity — because the release pipeline completed the disks' first boot while testing them, then published those same disks. Both images are withdrawn and are no longer downloadable. The boot test now runs on a throwaway overlay, and the build proves the published disks still seal themselves independently by booting them twice and requiring two different install identities.

  • The first-boot banner now appears on the hypervisor's own console. It carries the address to open and the only copy of the generated administrator password, and it was going to a serial port that Hyper-V Generation 2 machines do not have — so the appliance looked dead while it was serving normally. It also persists above the login prompt instead of scrolling past once.
  • Port 80 answers. It serves the application, redirects /admin to the administration console, and shows a self-refreshing page while the app is still starting. Previously all three ports refused connections for the first few minutes, which is indistinguishable from a broken image.
  • An interrupted first boot repairs itself. Secrets are written atomically, and the appliance no longer trusts a marker vouching for files it never finished writing.
  • Booting with only one of the two disks attached now boots, serves port 80 and says which disk is missing, instead of dropping to an emergency prompt with no login.

If you ran a 0.4.0 or 0.4.1 appliance: treat that install's generated credentials as compromised. Replacing only the OS disk preserves the credentials on the data disk; an OS upgrade alone does not rotate them. Restrict access and contact support for recovery guidance before continuing to use that installation.

Schema migrations: none over 0.4.1.