Repository navigation
PU — EmuFramework v1.0.2
PU — EmuFramework v1.0.2
Summary
This proactive update makes container updates and restores durable, removes unauthorized actions from delivered metadata, and corrects Report Designer canvas sizing.
Improvements
- Adds an atomic, phase-based maintenance journal with explicit rollback and recovery-required status.
- Checkpoints and closes both SQLite databases during graceful application shutdown.
Fixes
- Restores the previous container and the pre-operation persistent-data snapshot when update health verification fails.
- Compensates interrupted update and restore phases idempotently and retains recovery artifacts when automated rollback cannot finish.
- Requires stable
X.Y.Zupdate targets and supports a fail-closed local-image mode for unpublished test images. - Omits unauthorized form and line actions from
/api/metadata, while direct action calls continue to return403. - Filters hidden or disabled actions defensively in the client.
- Calculates Report Designer canvas width from left and right margins, including asymmetric margins.
Breaking changes and migration
None. The maintenance API adds optional phase, rollbackStatus, and recoveryRequired fields while preserving the existing status field.
Upgrade notes
Back up data.db and designer.db, preserve .emu-secret.key, and update both the application and updater images together to 1.0.2. After restart, verify login and Settings → System Maintenance diagnostics.
Validation
The candidate passed the offline release policy, type checking, automated tests, production builds, fresh-container boot, local-image upgrade, failed-health rollback, failed-restore rollback, and byte-equality checks for restored data.db.
Known issues
The local Docker acceptance stack requires Docker Desktop to be running and the previous release image to exist in the local image cache; the verifier never pulls it automatically.