Lex App v2.0.0rc29
Lex App v2.0.0rc29
Release Notes
This release refines how Lex App records lifecycle and bitemporal history around model changes.
That matters for audit-heavy applications because history should describe meaningful business changes, not framework side effects created while calculations or setup routines are running.
This release reduces setup and initialization friction for Lex App projects.
This release improves packaging, dependency, container, or runtime configuration reliability.
Changelog
Added
- Additional setup and initialization support for project bootstrap and environment-specific configuration.
Changed
- History and lifecycle timestamps are aligned more closely with business-relevant model changes.
- Initialization behavior is more tolerant of project-specific client names, deployment targets, and generated run configuration.
- Packaging, dependency, image, or runtime defaults were adjusted for more reliable installation and deployment.
Fixed
- Reduced noise in history caused by framework-driven calculation or setup activity.
- Reduced setup failures caused by missing generated files, client naming differences, or incomplete environment assumptions.
- Reduced environment-specific packaging failures around generated files, package contents, or dependency resolution.
Improved
- Bitemporal records are more dependable for audit, reporting, and as-of analysis.
Maintenance
- Kept the distributable backend package aligned with the current v2 runtime expectations.
Upgrade Impact
- Apply database migrations before running history, audit, or calculation-heavy workflows after upgrading.
- Regenerate or review generated project setup files if the project relies on Lex App initialization commands.
- Rebuild application images or virtual environments so dependency and packaging changes are actually used.
