Moltaro 0.0.37-beta
Release date: 2026-09-06
Portal administrators can move applications between technically ready virtual machines regardless of VM ownership or type. VM ownership selection and readiness displays are clearer, while customer transfers remain restricted to their own applications and account-owned machines.
Highlights
Section titled “Highlights”- Select an optional VM owner by account name or owner email instead of entering an account ID.
- Use Shared or Dedicated transfer destinations with explicit administrator and customer access rules.
- Distinguish healthy Dedicated VMs, placement restrictions and genuine host failures on both VM pages.
Detailed changes
Section titled “Detailed changes”Application transfers
Section titled “Application transfers”Portal administrators may move any application to any technically suitable VM, including another account’s VM or an unassigned VM. Ordinary accounts may move only their own applications and only to explicitly account-owned VMs; foreign and unassigned destinations remain unavailable through direct API requests as well as the interface. Transfer does not change either the application owner or the VM owner. Availability, maintenance, service readiness and capacity checks apply when discovering destinations, reserving capacity and executing the queued transfer.
VM administration
Section titled “VM administration”Provisioning provides a searchable, optional owner-account selector with loading, empty, retry and clear states. Both the VM list and detail page show VM type beside the title and owner/capacity as ordinary properties. Dedicated type, an assigned owner and disabled automatic Shared placement no longer appear as host faults. Full capacity and intentional maintenance are action restrictions; genuine service, agent and provider failures remain visible. Deletion restrictions are shown with the delete action. Updated copy is available in English, Ukrainian, German, Polish and Spanish.
Existing Shared VMs and their applications retain their classification and automatic placement rules.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema or data migration is introduced. This is a Portal-only publication: existing Managed Apps remain on runtime 0.0.36-beta and are not restarted or upgraded. Portal and its bundled storage-signing services have a brief activation interruption. A PortalDb recovery point is created before activation; a failed activation restores the previous Portal release without a schema downgrade.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish using two-phase PortalOnly: prepare the frozen Portal/documentation artifact, inspect its prepared status, then promote with its frozen runner. Do not select runtime replacement or an update package. Runtime VM agents, runtime/update manifests and application containers remain unchanged.
After publication, verify Portal access, VM readiness and available transfer destinations. Moving an application still requires a fresh compatible referenced backup. This release does not create the final OMS backup or execute its transfer.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No runtime, Package SDK or agent protocol change. Customer transfer destinations must be explicitly assigned to the customer’s account; unassigned platform capacity is not a customer-directed transfer destination. Administrative transfers can cross VM ownership boundaries without transferring application ownership. No new configuration is required.