Moltaro 0.0.49-beta

Release date: 2026-09-08

Workspace administrators can inspect storage-confirmed progress of background file uploads without keeping abandoned transfers alive. File Protection also uses a single preview drawer when switching between sources and retained versions.

Highlights

• Observe a background upload’s exact session and originating job, including uploads created by system automation, without impersonating its creator.
• Distinguish confirmed transferred bytes from reserved capacity and unknown progress, without renewing upload activity or delaying cleanup.
• Switch File Protection source and version previews within one drawer; closing the preview or leaving the page cleans up its owned overlay.

Detailed changes

Background upload diagnostics

The administrator-only GET /api/workspace/files/uploads/administration/{uploadSessionId}/progress returns session, source run/job, status, declared size, observation time and nullable storage-confirmed byte/part counts. Ordinary and anonymous callers are denied. A missing session is HTTP404 for an administrator.

Only a successful observation of an unchanged, unexpired uploading session establishes a count. An empty provider inventory is zero; provider failure, invalid inventory, another phase, expiry or a concurrent session transition returns unknown counts. The response is not cached and exposes no storage locator, ETag or signed URL. Observation neither grants file access nor changes upload activity, leases, reservations or cleanup eligibility. Normal upload resume keeps its existing activity behavior.

File Protection previews

Source and retained-version previews share one replaceable drawer. The preview uses the standard narrow width and outside-click dismissal. Switching from history to a version preserves overlay ownership instead of leaving stacked or prematurely closed previews. Operator guidance clarifies the distinction between downloading a retained file and restoring it into its originating application.

Database and upgrade impact

No new database schema or business-data migration is introduced relative to the previous production runtime. Managed Apps receive a full runtime replacement with a short per-application interruption. Existing files, upload sessions, backups, schedules and Object Storage bindings remain in place. The release workflow creates its normal database recovery points before activation.

Deployment and operator actions

Deploy using ReplaceRuntime, updating Portal, both StorageSigner replicas and all three Managed App runtimes from one prepared source. Keep Runtime VM agent version 0.1.45; its normal release artifact and fleet verification still apply. Do not install only the new runtime while leaving an older StorageSigner: the observation route must be present in both components. An unavailable observation remains unknown; it never falls back to the activity-renewing resume route.

This release does not enable synchronization schedules, start imports, cancel jobs, change customer source code, or process the existing backlog. After installation, the synchronization owner performs the separately authorized interruption/replay acceptance. Check that the administrative endpoint is installed and authorization works before relying on it for that observation.

Compatibility and breaking changes

The administrative endpoint is additive. Creator-owned upload APIs and ordinary resume semantics are unchanged. Deploy runtime and StorageSigner together. Provider integration implementations of IFileBodyStore must implement the separate read-only observation method without renewing upload activity.

Existing PDF preview/browser-save acceptance and full synchronization acceptance remain separate open items; this release does not claim to fix or accept them.