Moltaro 0.0.46-beta
Release date: 2026-09-07
File Protection keeps restore access current in already-open History views. The Source drawer and full details page show newly created or revoked restore access automatically, without reopening the page or changing the Source.
Highlights
Section titled “Highlights”- See active restore access update automatically in open Source History views.
- Keep the selected recovery point and visible content stable during refresh.
- Clear permission-sensitive history when access or authentication changes.
Detailed changes
Section titled “Detailed changes”Live restore access in History
Section titled “Live restore access in History”An open History view previously could keep an outdated list of active restore sessions even while its Source and protection status were current. History in the Source drawer and details page now refreshes active restore access while visible. A session created or revoked elsewhere no longer requires a Source change, browser reload or reopening the drawer to appear correctly.
Refresh keeps loaded content, the selected recovery point and current item selection visible. Recovery-item pages are loaded when selected or explicitly refreshed; updating active sessions does not repeatedly read all retained files. The behavior applies to desktop and narrow mobile layouts.
Permission-sensitive history
Section titled “Permission-sensitive history”History content is cleared when the current user loses the required permission or authentication. Late responses from an earlier request cannot repopulate a cleared view. Reauthentication also clears obsolete pending-action state so it does not leave the Source’s actions incorrectly busy.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema or data migration is introduced. The managed rollout uses a full runtime replacement, with a short interruption for each application. Existing Sources, schedules, Agent assignments, storage bindings, protected versions and restore history remain in place. No Object Storage is copied, recreated or deleted by this correction.
Keep the existing recovery points. Rolling back binaries restores the previous History display behavior; it does not undo retention already applied to stored objects. Retained objects must remain intact.
Deployment and operator actions
Section titled “Deployment and operator actions”Deploy through the normal two-phase ReplaceRuntime workflow, not an update package. No new repository, storage provisioning, credential change, Agent reenrollment or additional activation Stop/Start is required.
After the rollout, verify that creating and revoking restore access through the normal application interface updates both already-open History views without reloading or altering the Source. Keep the previously verified recovery points; this display correction does not require another full backup or byte restore.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No known compatibility or breaking changes. Runtime API, Worker, File Protection Agent protocol, storage and persisted contracts are unchanged. File Protection protocol remains 2.1; Runtime VM agent remains 0.1.45.