Moltaro 0.0.10-beta

Release date: 2026-08-06

Moltaro 0.0.10-beta introduces managed Object Storage for large file bodies, governed Board constraints and statements, and the Operational Location foundation. It also removes ClamAV from the baseline runtime while preserving mandatory streaming integrity and content verification.

Highlights

Managed large-file storage

• Managed Apps can use an isolated private S3-compatible bucket for new file bodies while existing database and local-file bodies remain readable.
• Browser, API, and Package SDK uploads use resumable multipart transfers with bounded memory use, exact size and SHA-256 verification, signature and MIME checks, and durable retry state. Supported uploads can reach 2 GiB without buffering the complete file in WebApp, API, Worker, agent, or Portal.
• Each Managed App has an exact 500 GiB storage limit, deterministic retention and garbage collection, bounded expired-upload cleanup, provider inventory, and app-scoped API and Worker signer capabilities. Storage credentials are never delivered to a Managed App or Runtime VM agent.
• Managed backups now use verified file-body reference snapshots. They pin the immutable Object Storage generations required by a restore instead of embedding those bytes in every backup archive.
• Portal adds operator diagnostics for accounts, buckets, signer replicas, capacity, rollout state, backup references, garbage collection, and runtime integrity. New S3 uploads are enabled only through a stopped-app, administrator-controlled and audited rollout.

File verification and antivirus policy

• Mandatory checksum, size, binary-signature, MIME, and image-safety checks remain active for every uploaded body.
• Malware scanning is now a separate optional operator-managed policy. The baseline package uses MalwareScanning.Provider=None and contains no ClamAV image, service, signatures, volume, health dependency, or resource reserve.
• Full runtime replacement removes legacy ClamAV environment entries, orphan containers, and the package-owned signature/runtime directory. A future ClamAV activation requires an explicit audited operator workflow and is never inferred from old host files.

Boards governance and runtime reliability

• Administrators can define reusable Board Statements and bind governed transition, entry, exit, and status-invariant constraints to Board workflow.
• Authoring includes validation, dependency-aware lifecycle checks, preview diagnostics, localized errors, and explicit release boundaries.
• Board link candidate search now executes through a scoped server-side query pipeline, and target Entity search uses the live configured search contract.
• Runtime loading no longer blocks on realtime connection lifecycle, rank positioning is corrected, and reference-field behavior receives the required runtime context.

Operational locations and everyday usability

• Operational Locations establish a shared identity, address, Geo Zone, and effective IANA time-zone foundation for later scheduling and location-aware modules.
• Built-in File System folders are localized, Data Explorer multi-sort semantics are deterministic, and object drawers use space more effectively.
• Package SDK attachment transfers use the same bounded, verified file-body contract as product upload surfaces.

Database and upgrade impact

Both Workspace and Portal databases change during the coordinated full replacement. Workspace changes add governed Board statements/constraints, durable managed uploads, verification and deletion safety, backup snapshots, provider inventory/retention, Board search support, and attachment-transfer publication context. Portal changes add managed file-body storage/signing, referenced backups, multipart agent state, binding/version controls, rollout state, and operational telemetry. Portal and Managed App recovery points must be retained through acceptance; this release is not a delta update.

Runtime and deployment

• WebApp, API, Worker, RabbitMQ, Workspace UI toolchain, Package SDK, moltaroctl, Portal, public documentation, storage signer, and Runtime VM agent 0.1.35 form one release boundary.
• Existing Managed Apps require a full runtime-package replacement so the Workspace schema, runtime files, containers, storage contracts, and package assets advance together. This release is not published as a delta update.
• The Portal release provisions two loopback storage-signer replicas and separate credentials for platform artifacts and managed file bodies.
• Runtime VM agent 0.1.35 uses the direct authenticated Portal command path, holds no Object Storage account credentials, and is the minimum version for managed file-body rollout operations.
• New Managed Apps select the published 0.0.10-beta base runtime and start with malware scanning disabled unless a separate operator-approved policy is activated.
• Backup deletion and retirement of old runtime or agent artifacts remain explicit operator decisions after production validation.