TestVibe 0.4.18
All release notes · Self-hosted upgrade guide
2026-10-19. Self-hosted packages published from application source
313af3179a4d0478137429004362b878e961290e, tagged v0.4.18.
This page records the published build and its validation scope. The customer portal lists the versions currently offered for each format; website-feed promotion and customer download verification are separate delivery steps.
Changes since 0.4.16
- Client-side request/history correlation IDs support plain HTTP appliance
contexts where
crypto.randomUUID()is unavailable. These IDs are not authentication credentials. - Appliance packaging includes backup helpers and a first-boot readiness guard; the restore helper opens private database dumps through root-opened standard input. Historical upgrade and restore acceptance was not run for this release.
- The database scripts advance from V0312 through V0321, including reusable test and authoring-block metadata, artifact indexes, agent-plugin OAuth, model registration, knowledge history/budgets, and project branches. Apply pending migrations before the new application starts.
These points describe the source and package changes. Runtime acceptance scope is recorded below.
Published packages
The complete stack is published for Linux x86-64 (linux/amd64). The
customer-registry images and Helm chart use version 0.4.18.
| Package | Intended deployment | Bytes |
|---|---|---|
testvibe-selfhosted-v0.4.18.zip | Docker Compose and bundled Helm chart | 42,175 |
testvibe-selfhosted-v0.4.18.tar.gz | Alternate Compose/chart archive | 30,722 |
testvibe-0.4.18.vhdx.tar | Hyper-V; paired OS and data disks compressed with Zstandard | 3,563,335,680 |
testvibe-0.4.18.ova | VMware / VirtualBox; includes both disks | 4,191,119,360 |
Customer images are hosted at testvibe.azurecr.io: testvibe-web,
testvibe-blobserver, testvibe-migrations, and testvibe-runner. The chart is
oci://testvibe.azurecr.io/charts/testvibe, version 0.4.18.
Verify downloaded files against the matching SHA256SUMS catalog. The final
catalog's SHA-256 is
20f6a61bef0038df944cc74a77e42660915709a0f77747a59d43ffae24c9f423.
Only use download formats and versions actually offered on the portal.
Validation scope
The release publication recorded successful source/version/tag checks and immutable image/chart identity checks, a web-image credential-leak scan, disposable appliance source-identity and unique-installation/sealing checks, disk-content comparison after VHDX/VMDK conversion, OVA structure and embedded manifest verification, full decoding/signature checks of both VHDX streams, and local payload/checksum integrity checks. Storage publication checks confirmed object existence and byte length; they did not perform a remote payload readback or hash verification.
The retained release payloads' exact byte sizes and SHA-256 hashes were also independently rechecked after publication. Verification of the copies delivered through storage or the entitled portal is a separate delivery gate.
Waived or not run
- Product provisioning, deterministic runner, and selected smoke scenarios were not rerun for this publication, at the user's request. Earlier smoke results are not recorded as passes for this publication.
- Historical upgrade, restart, and logical/paired backup-restore acceptance were not run and explicitly waived.
- Final local native runtime acceptance was waived.
- Actual customer Hyper-V, VMware, and VirtualBox imports were not tested.
Published VM formats do not establish customer-hypervisor import acceptance.
Before upgrading
Follow the upgrade procedure and backup guidance. Preserve the database, artifact storage, installation identity, configuration, and encryption keys. Apply all pending PostgreSQL migrations before starting the new application.
For an appliance upgrade, preserve the existing data disk and attach only one
disk labeled testvibe-data. The historical upgrade/restore paths above remain
outside this release's completed acceptance checks.