Moltaro 0.0.43-beta
Release date: 2026-09-07
Schedule File Protection directly on each Source, follow useful backup progress and let the Worker maintain retained recovery data. This release also extends Task Definition configuration and fixes trusted file references and API liveness.
Highlights
Section titled “Highlights”- Source-owned CRON schedules, bounded retries, operation results and notifications.
- Worker-owned verification and repository maintenance, independent of an online Source Agent.
- Task Definition roles, participant admissions, assignments, permissions and collaboration settings.
- Correct trusted C# file-reference handling and dependency-free API liveness.
- Runtime VM health no longer fluctuates because an old backup-cleanup command failed.
Detailed changes
Section titled “Detailed changes”File Protection Sources can schedule automatic protection with a CRON expression and time zone. Operations report useful work, waiting, attempts and outcomes. Unchanged content renews verified retention without publishing another recovery point. Source permissions govern filenames, schedule access and cancellation; desktop and mobile controls are available in all five supported languages.
The Worker now owns final verification, retention renewal and repository maintenance. The manual maintenance operation is removed. Recovery points, checkpoint references and active restore sessions remain protected while maintenance advances. Agent concurrency is Source-scoped; stale leases and exhausted waiting are fenced before acceptance. Packaged Worker configuration includes its narrowly scoped storage and TLS verification access.
Task Definition configuration gains runtime-role mappings, Owner/Responsible admission and assignment policies, finite permission grants and collaboration settings. These are configuration capabilities; they do not introduce new Task Instance commands or implicit administrator access to business data.
Trusted C# Entity mutations preserve their intended file-reference scope across updates and retries. The ordinary persisted Entity authorization path remains authoritative for untrusted requests.
The API liveness endpoint returns process health without resolving a workspace, database-backed license service or dependency health checks. Readiness still checks dependencies. Portal backup reconciliation no longer replays deleted snapshot cleanup history against a transferred application’s new VM, and command failures no longer overwrite heartbeat-owned VM health.
Database and upgrade impact
Section titled “Database and upgrade impact”Workspace databases are upgraded during a full runtime replacement. Each application has a maintenance interval while its API, WebApp and Worker are replaced and its database migrations run. Portal is also updated, with its own recovery point. There is no new PortalDb migration in this release.
Existing recovery identities and retained data are preserved. Pending legacy manual maintenance commands are cancelled; automatic Worker maintenance replaces that command path. Accepted backup content awaiting finalization is independently verified before publication. Task Definition settings and historical operation receipts receive the supported new defaults without inventing administrator grants.
Retain the pre-upgrade database recovery points and the original referenced Object Storage. Do not treat an old-runtime restart or database-only restore as a complete rollback after new operations have changed durable storage state. Recovery must follow the supported package/database and retained-object boundary.
Deployment and operator actions
Section titled “Deployment and operator actions”Use Production ReplaceRuntime for all three current Managed Apps, through
release prepare, status inspection and the prepared frozen promotion runner.
Publish package 0.0.43-beta and Runtime VM agent 0.1.45. Do not reuse the older
local File Protection feature package as the production artifact.
The prepared artifact must pass both migration-model checks, package inspection and the all-application compatibility preflight before activation. After replacement, verify exact package/image versions, API liveness/readiness, Worker/Gateway health, backups and the selected File Protection customer flow.
Install the Agent and Restore tools distributed by the released runtime; File Protection uses protocol 2.1 and its pinned Kopia distribution. Existing installations must use the generated Worker capability/CA configuration; never copy Gateway server private keys into the Worker.
The initial production File Protection verification is a bounded, explicitly selected application canary using existing storage. Physical provider deletion, mature pack rewriting and larger capacity profiles are not certified by this release. No separate test storage resources are provisioned.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”File Protection Agent protocol 2.1 and the removal of the manual maintenance command require clients to use the matching released distribution and supported Source operations. Existing credentials and retained recovery objects are not rotated or deleted merely to publish this release.
Tasks configuration contracts advance to 1.6.0. Consumers must use the supported role, assignment, permission and collaboration settings; no legacy configuration fallback or implicit runtime permission is added. Liveness must not be used as a substitute for readiness when admitting application traffic.