Moltaro 0.0.38-beta
Release date: 2026-09-06
Moving an application to another Runtime VM no longer rereads all uploaded files when the application keeps its existing Object Storage binding. Transfers validate the backup and its file catalog without a redundant full-storage scan.
Highlights
Section titled “Highlights”- Avoid a full file-body download and checksum scan during same-application VM transfers with unchanged storage.
- Retain backup archive, catalog integrity and ownership checks before cutover.
Detailed changes
Section titled “Detailed changes”An active Runtime VM transfer reuses the validated catalog’s immutable object references, hashes and provider versions when the application identity and Object Storage binding remain unchanged. The transfer’s preparation cost no longer includes downloading every referenced file body through Portal. The operation step identifies catalog validation, and its audit record distinguishes catalog reuse from a full file-body verification.
This optimization applies only to a matching active transfer recorded by the server. In-place backup recovery and copying to a different application/storage binding retain their full file-body verification. Administrative/customer access rules, source shutdown, restore holds, target capacity, runtime compatibility and failure recovery remain unchanged.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema or data migration. This is a Portal-only publication; all existing Managed Apps remain on runtime 0.0.36-beta without restart or upgrade. Portal and its bundled storage-signing services have a short activation interruption. A PortalDb recovery point precedes activation and the previous Portal release is retained for rollback.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish using two-phase PortalOnly. Do not replace runtimes or publish runtime/agent/update artifacts. The cancelled OMS transfer is not restarted by this release. Start a new transfer explicitly after checking the backup’s freshness and ensuring application writes are paused; changes after the selected backup are not included in the restored database. Preserve the existing Object Storage binding and bucket.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No known API, SDK, agent or runtime compatibility changes. A VM transfer with unchanged storage is no longer a full-storage integrity audit. Independent backup recovery continues to verify referenced file bodies.