Moltaro 0.0.42-beta
Release date: 2026-09-06
Fix Runtime VM transfers interrupted when background cleanup removed an archive still needed by the destination VM, and restore file-access confirmation after repeated transfer attempts.
Highlights
Section titled “Highlights”- Keep recovery control archives available throughout an active VM transfer.
- Confirm file access correctly after repeated credential rotations.
- Continue cleaning unused archives after operations complete.
- Preserve the application’s identity, ownership and existing Object Storage.
Detailed changes
Section titled “Detailed changes”Background cleanup now preserves the exact control-state archive and reference catalog assigned to an active transfer. Transfers that start while cleanup is listing stored artifacts are also protected. Completed operations and orphaned artifacts remain eligible for cleanup; backup retention is not disabled.
File-access cache invalidation now sends credential identifiers in bounded batches. Repeated transfer attempts no longer exceed the signer’s request limit. Every signer replica must still confirm invalidation; revoked credentials are included so old cached authorization is removed.
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. Publication does not restart their containers. A separately initiated transfer stops only the selected application while its matching backup is restored on the target.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish using PortalOnly preparation and the frozen promotion runner. Do not replace runtime packages, agents or application containers. Agents remain 0.1.44. Before retrying a failed transfer, confirm that rollback has finished and the target has been cleaned. Keep writes and background work stopped for the selected backup-based transfer. Retain the existing Object Storage; file bodies are not copied to the new VM.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No SDK, ownership, storage-binding or schema change. The correction works with the published agent 0.1.44 and exact runtime 0.0.36-beta. It changes retention of temporary transfer artifacts, not the contents or format of customer backups.