Skip to main content

TestVibe 0.4.12

All release notes · Self-hosted upgrade guide

The first-customer-feedback release, plus the appliance's first network setting. Every issue from the first real on-prem onboarding, fixed — and the ask that came out of it built: point the appliance at your own DNS. All four artifacts are published: containers, Helm chart, VHDX and OVA. (There is no 0.4.11 — it was cut and withdrawn before any artifact reached customers; everything it contained ships here.)

  • Point the appliance at your own DNS. A new Network page in the administration console takes upstream DNS servers and search domains — the resolv.conf equivalent — and the appliance applies them within about a minute of saving, no restart. Settings live with your data, so they survive OS-disk upgrades. Internal SMTP relays and SNI-based internal sites work by hostname; clear both fields to return to plain DHCP. Setting servers routes all lookups to them; setting only search domains keeps the DHCP servers and adds the list.
  • The first user can always be created. An appliance whose data disk was sealed before the first-user bootstrap token existed never got one, so the console's First user card sat permanently disabled with a hint about environment variables an appliance operator has no way to set — there is no OS login, by design. The first boot on 0.4.12 backfills the token pair into the existing data disk; the card simply works.
  • A pasted license activates even when the paste was line-wrapped. Email clients, PDFs and terminals wrap long lines, and the verifier used to fail such a paste with a generic message. The transport damage is now stripped before the signature check, in the app and in the console. A pasted license also takes effect in about 20 seconds, signed-in users included — the console now says exactly that instead of suggesting a restart, and storing a license into a database with no instance row fails with an explanation instead of toasting success.
  • Deleting a user from the administration console works. The owned-account guard was written as a query PostgreSQL rejects while parsing, so every delete failed with a raw 22P02 error and deleted nothing. It is now a real check with a plain sentence.
  • The console reads like a settings screen, not a manual. Every page shows label, control and status; explanations moved behind small info dots (hover or tap), environment variable names appear only when a value is actually pinned in the environment, and reference notes collapse until asked for. Sign-in providers became connectable cards — GitHub, Google, and one OpenID Connect slot with presets for Microsoft Entra ID, Okta, Keycloak, Auth0, Ping and GitLab that pre-fill the issuer shape.
  • License problems no longer wear the credits dress. A lapsed or missing license used to surface in the app as "Out of credits / Buy credits" — on an install that has no credits and nothing to buy. It now raises a License required prompt that opens Settings → License, and every credits surface (header pill, dashboard gauge, Billing and Credit Usage panels) is gone on self-hosted installs.
  • Corporate mail relays with private certificate authorities work. Paste your CA certificate (PEM) into the new Trusted certificate authority mail setting — trusted for the mail connection only — or, as a last resort, switch on Skip certificate verification. Implicit-TLS port 465 is now supported alongside STARTTLS.
  • Custom AI endpoints are editable in place, and connection failures name the URL and the actual failure instead of "Resource temporarily unavailable". Sign-in fields are readable in dark theme, the console shows the web app's address on the People page, and the SSO redirect URI reflects your configured public URL on the appliance instead of 127.0.0.1.

Upgrading: Docker — take this release's docker-compose.yml first (a pull alone re-pulls your pinned tags), then docker login testvibe.azurecr.io, docker compose pull, docker compose up -d. Kubernetes — helm upgrade to chart 0.4.12, passing the same secrets you installed with. Appliance — replace the OS disk with the 0.4.12 one and keep your data disk; works from any 0.4.2+ data disk, and the first boot adds the first-user bootstrap token to data disks that never had one.

Schema migrations: none. Upgrading from 0.4.10 swaps code only, and rolling back to 0.4.10 is equally safe. Take a backup before any upgrade regardless.