Skip to main content

TestVibe 0.4.4

All release notes · Self-hosted upgrade guide

Archived release. No installation packages remain attached to this release. Use the current version.

Tagged but never published. There are no 0.4.4 containers, Helm chart or appliance image — the version exists as a tag and nothing else. It is documented here because its headline fix is one you should know about: everything below reached customers in 0.4.5 (containers and Helm chart), and reaches appliance users in the next appliance image.

  • Self-hosted installs were silently deleting customer data to satisfy a quota nobody had bought. You do not subscribe to a plan on-prem, so every workspace carried the implicit Free tier's 1 GB allowance — and past it, an hourly reaper permanently deleted the oldest telemetry day and the oldest artifact-bearing run's files, with no setting to turn it off and no log line to notice it by. Worse, the Free-inactivity purge fired too — a quiet appliance is by construction a workspace on the Free plan with no run in 30 days — and that one wiped all telemetry and every run's artifacts, not just the oldest. Since this release:
    • Quota can never justify a delete on a self-hosted install. There is no quota enforcement on-prem, on the write side or the delete side.
    • The inactivity purge does not run on-prem at all.
    • Retention is strictly opt-in. The cloud's 30-day telemetry default does not apply: unless you set a retention period yourself, nothing is deleted. A period you do set is honoured exactly, and is never widened by how full the disk is.
    • Every destructive step now logs what it removed and why, and the storage screens stop quoting a quota that does not apply to you.
  • The console's concurrency fields named the wrong pool, and nothing read them. Capacity limits set in the administration console now apply to the pool they describe.
  • The console answers "how do I upgrade this?" for the deployment it is actually running on, with a preflight, a backup story and visibility of host patching.
  • Appliance. A sealed OS disk booted without its data disk no longer advertises an address and password that no longer work; the two public URLs are handed to the administration console instead of being pinned into testvibe.env, on fresh appliances and on ones already in the field; and the image owns its OS patching policy instead of inheriting one.

Schema migrations: none over 0.4.3.