Moltaro 0.0.41-beta
Release date: 2026-09-06
Fix Runtime VM transfers that stopped with an authorization error while sending their recovery control archive. The destination can retrieve the exact runtime package, backup and control archive required to restore the same application.
Highlights
Section titled “Highlights”- Allow the active transfer to upload its bounded recovery control archive.
- Allow the destination VM to download the exact artifacts assigned to it.
- Preserve the application’s identity, ownership and existing Object Storage.
Detailed changes
Section titled “Detailed changes”Transfer archive uploads now use the existing resumable multipart mechanism. Authorization remains bound to the active server-side operation, source VM, application, backup and storage binding. Incorrect object keys, stale attempts, other VMs and completed operations are rejected. The destination receives only the exact artifacts recorded in its restore command. Existing backup upload limits and protections remain in effect.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema or application runtime change. Portal publication causes a short Portal interruption and retains a PortalDb recovery point and the previous Portal release. All three applications retain runtime 0.0.36-beta and their containers are not restarted by publication. A separately initiated transfer stops the selected application while its fresh backup is restored on the target.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish with two-phase PortalOnly preparation and its frozen promotion runner. Do not rebuild or replace Runtime VM agents, application packages or containers. Agents remain 0.1.44. Failed transfers are not automatically retried. Stop writes and background work, create a fresh matching backup, then initiate the transfer. Retain the existing Object Storage: referenced file bodies are not copied.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No SDK, application ownership or schema change. This correction uses the already-published agent 0.1.44 transfer protocol and exact runtime 0.0.36-beta. In-place recovery, copy-as-new and transfer remain separate operations.