Skip to content

FU — EmuFramework v1.3.0

Choose a tag to compare

@emu479p01 emu479p01 released this 22 Sep 13:43
· 6 commits to master since this release
9f205f0

FU — EmuFramework v1.3.0

Summary

App-local Recent navigation, selected-model deployments, Apps & Models administration, and optional offline ISV licensing.

Improvements

  • Sidebar activity follows the original app menu, including Recent shortcuts and record detail routes. Recent history retains ten entries per user per app, with a separate Settings history and existing Favorites preserved.
  • Designer builds complete selected-model packages for vendor updates (SYS/ISV/LOC) or UAT-to-Prod promotion (all layers). Preview identifies metadata additions, changes, removals and preserved models; ownership conflicts, missing dependencies and incompatible customizations block deployment. Unselected models and physical business data are retained.
  • Change-set apply revalidates the candidate and restores runtime registrations and database changes on synchronous apply/persistence failures.
  • System administration lists app/model layers, source, metadata revisions, dependencies, deployment history and license state.
  • Optional ISV requirements use installation/customer-bound Ed25519 license files, a seller CLI, vendor trust registration, monotonic renewal sequences and audit records. Expiry restricts the app and dependent apps to read-only use; renewal takes effect without redeployment.

Breaking changes and migration

None for existing apps and packages. License tables are created automatically in the designer database; existing models remain unlicensed. Recent returns an additional app property and up to ten entries per app rather than ten globally. Selected-model packages use schema version 2 and require 1.3.0 at the destination; legacy version-1 packages remain supported.

Upgrade notes

Back up the data and designer databases together. Update application and updater images together to 1.3.0. Use metadata packages for UAT-to-Prod promotion; each environment keeps its own installation identity and licenses. Read Model deployment and ISV licenses for deployment modes, seller CLI usage, renewal and recovery.

Validation

Version consistency, type checking, production builds and automated tests pass (131 core, 39 client, 155 server and 6 release-policy tests; one optional legacy-backup fixture test is skipped). Tests use Node 24 and bounded worker concurrency. The 1.2.0-to-1.3.0 persistent-database upgrade check passed for existing login, business data, CUS fields/models, Recent/Favorites, legacy package preview and additive license storage. Browser checks verified desktop/mobile menu activity, app-local Recent, Apps & Models and layer selection in both deployment modes. Release-policy validation passes against 1.2.0. This branch is not published.

Known issues

Offline licensing cannot prevent changes by operators controlling the server, source, database or clock, and has no online revocation or key rotation. Trusted scripts/native code are not sandboxed. External side effects cannot be rolled back; a machine failure between commits to the separate data/designer databases requires backup recovery. Dynamic customizations still require UAT validation. New long-tail administration/Designer labels remain English. License notices in an already-open page update on refresh.