Moltaro 0.0.12-beta
Release date: 2026-08-08
Moltaro 0.0.12-beta completes the managed multipart-upload path across the
product, strengthens governed record matching and generated-context writes, and
ships a more compact and predictable object-detail experience.
Highlights
Section titled “Highlights”One managed upload path
Section titled “One managed upload path”- File System, attachments, Entity File fields, reference pickers, and Boards now use the same resumable multipart-upload implementation and lifecycle UI.
- Upload sessions persist their authorization owner, origin, verification
policy, malware policy, and maximum-size snapshot. Completion remains gated
on an available published
FileReference. - Closing or reopening a picker cannot resume an abandoned submit into a new interaction. Cancellation, session persistence, refresh timing, and availability transitions are handled consistently.
- Runtime cleanup expires abandoned sessions in bounded batches and retains terminal session history for 30 days.
- API ingress streams request bodies instead of buffering multi-gigabyte uploads in the Web container. The application remains the authoritative, localized file-size gate.
File integrity and migration correctness
Section titled “File integrity and migration correctness”- Legacy database-to-S3 migration now preserves a completed inspection across
the new content generation and re-keys any open inspection job. A migrated
file can no longer report
Availablewhile being rejected as uninspected. - File-reference operations, record merge, cleanup, signer access, durable audit, and Package SDK save invariants use the same managed-body contract.
Boards, drawers, and record matching
Section titled “Boards, drawers, and record matching”- Board item and Entity drawers use a shared, pinned navigation model with compact destinations, consistent breadcrumbs, stable section routing, and more usable workspace for record content.
- Board process attachments use the governed managed-upload policy context.
- Duplicate matching and record merge now preserve honest result states and surface bounded conflicts instead of presenting incomplete outcomes as success.
Agent and developer documentation
Section titled “Agent and developer documentation”- Generated agent documentation is now an immutable release artifact with a machine-readable source revision, documentation version, build time, and stable ETag behavior.
- Public documentation now records release-sensitive extension behavior and provides the supported atomic related-Entity graph recipe.
- Generated-context transactions reject a later Entity identity that was not part of the first ordered lock batch. Stage the complete related graph and save it once, or use separate explicit transactions.
Database and upgrade impact
Section titled “Database and upgrade impact”Each Workspace database changes during its replacement window to add governed upload-session authorization, origin and policy snapshots, and verification constraints. Existing data remains valid and receives safe defaults. There is no PortalDb change.
Portal and package delivery
Section titled “Portal and package delivery”- Portal installation-package uploads use their configured 100 MiB ceiling rather than ASP.NET Core’s smaller transport default.
- The obsolete
/w/defaultpackage route is removed. Moltaro continues to resolve its single workspace exclusively from deployment configuration. - Portal, public documentation, API, WebApp, Worker, workspace migration, Package SDK, package templates, and the base runtime are released together.
- Deployctl normalizes generated remote scripts to Unix line endings before Bash execution, so a release launched from Windows cannot fail an SSH preflight because of CRLF transport artifacts.
- Existing Managed Apps are advanced through full runtime replacement, not a published delta update. Backups and old runtime artifacts remain subject to explicit manual retention decisions and are never deleted automatically.