Skip to main content

TestVibe 0.4.13

All release notes · Self-hosted upgrade guide

15 September 2026. Easier test creation, clearer runs, and a dedicated home for automations.

  • Choose where a new test belongs. The New test dialog includes a searchable folder picker for writing, describing, recording, and importing tests. The selected destination survives switching creation methods, and rejected requests retain the details needed to correct them and try again.
  • Clearer tests and runs. Compact test trees, simpler generation progress, and separate test-selection dialogs make long projects easier to navigate. New run, New load test, and New automation name their actions. A refused run keeps its selection and settings available for retry. Run-result events retain their order, and reopening a project link or moving through browser history selects the linked project.
  • Automations has its own home. Manage schedules and run-triggered actions in Automations. Paused automations are labelled clearly. GitHub workflow setup also lives here: choose tests and triggers, create a setup pull request, and review it before merging. Workflow credentials are restricted to their repository and selected scope. See Automations.
  • More useful shared context. Project notes support nested folders, and the Assistant uses shared project knowledge across its work. Conversation progress, generation activity, and proposed fixes are easier to follow without exposing internal tool output.
  • Stronger account and API checks. Changing or resetting a password revokes older sessions. Existing API keys are checked against current membership and permissions. Retrying a run request with the same idempotency key cannot silently start duplicate work.
  • Self-hosted packaging fixes. The administration-console image includes its required application files. Appliance descriptors use the disks' actual virtual capacities.

Scope: Repository workflow templates target GitHub Actions. Feature adaptation requires hosted TestVibe: review can hold suggestions for approval, or auto-accept can apply a valid update after a successful background review if the feature is unchanged. Accepted instructions still need regeneration and a test run. Email is the only external notification channel; Slack, Google Chat, and Teams delivery are not available.

Upgrading: take the 0.4.13 Compose bundle before pulling images, or upgrade to Helm chart 0.4.13 with your existing secrets. For the appliance, replace the OS disk and keep the existing data disk. Back up the database and artifact storage before upgrading. Recovery requires the matching database and artifact backups; a code-only rollback does not undo the schema changes.

Schema migrations: 13 (V0283–V0295) since 0.4.12. These add project knowledge folders, Assistant job state, session revocation, GitHub delivery recovery, and repository workflow credentials and proposals, and refresh the model catalog. Migrations apply automatically through the supported installation path and are forward-only.