Moltaro 0.0.45-beta
Release date: 2026-09-07
File Protection accepts valid Hetzner retention responses during backup finalization and shows consistent live progress across the operation list, Source drawer and a new full Source details page.
Highlights
Section titled “Highlights”- Fix backup finalization rejecting valid COMPLIANCE retention metadata from Hetzner Object Storage.
- Show uploading, verification and retention progress consistently without confusing a configured Source with a successfully protected file.
- Open Source details at a permanent address and manage schedules in a dedicated section.
Detailed changes
Section titled “Detailed changes”Backup finalization and retention
Section titled “Backup finalization and retention”Some S3-compatible responses omit the AWS XML namespace and report retention deadlines with nanosecond precision. File Protection now accepts the supported namespace-free response as well as the AWS form. It continues to require unambiguous COMPLIANCE retention and to verify the exact stored object version and its deadline after an extension. Retention is never shortened or bypassed.
The correction applies to initial recovery-point publication, unchanged-file retention renewal and maintenance checkpoint certification. A failed earlier operation is not retroactively marked successful; start a new normal protection request after the upgrade and verify that a recovery point is published.
Live operation status
Section titled “Live operation status”The Source table, mobile cards, drawer and details page now share live operation state. Background refresh preserves visible content and open-menu focus instead of repeatedly displaying loading placeholders. Upload progress shows transferred bytes; verification and retention remain active until the server reports success. Reaching 100% upload alone does not report successful protection.
Actions reflect the current assignment and operation. An already assigned Agent is changed through the secondary menu; Assign Agent is no longer presented as the primary action for an assigned Source. Permission changes clear content that the current user may no longer view.
Source details and schedules
Section titled “Source details and schedules”Each Source has a full details page at /file-protection/sources/:sourceId,
accessible from the list or drawer and usable after reload. The latest operation,
Source properties and recovery history reuse the same content in both views.
Live progress remains visible in the details header while reading another
section. Facts adapt to desktop, resized drawers and narrow mobile displays.
A separate Schedule section shows enabled state, CRON expression, time zone, next occurrence and the latest occurrence result, with the existing schedule editor. The desktop table also shows the schedule. Updated interface text is available in English, Ukrainian, German, Polish and Spanish.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema or data migration is introduced. Managed applications receive a full runtime replacement with a short interruption per application. Existing Sources, schedules, Agent assignments, storage bindings, retention policies and stored versions remain in place. This release does not copy or delete primary or protected Object Storage.
Keep the existing recovery points. Rolling back binaries restores the previous behavior but does not undo already applied COMPLIANCE retention. Retained objects must remain intact.
Deployment and operator actions
Section titled “Deployment and operator actions”Deploy using ReplaceRuntime, not an update package. Publish the prepared Portal, runtime and Runtime VM agent artifacts through the normal two-phase workflow. Existing managed protection storage is already activated; do not repeat provisioning, change credentials or replace the repository for this fix.
After the rollout is complete and health is confirmed, run the normal protection and restore scenario against the existing Source and Agent. Verify initial recovery-point publication and an exact restore, then unchanged-file NoChanges renewal, the next file generation and restoration of both generations. An old failed run remains historical evidence, not a successful backup. Do not delete its stored versions or manually edit its outcome to make acceptance pass.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No known public API, Package SDK, Agent protocol or persisted-contract breaking changes. File Protection Agent protocol remains 2.1; Runtime VM agent remains 0.1.45. Existing Agent enrollment and Source configuration are retained. The new Source details address is additive; existing list and drawer entry points remain.