Changelog

Lex App v2.0.0rc61

Lex App v2.0.0rc61

Release Notes

This release reduces setup and initialization friction for Lex App projects.

It makes generated project configuration, client setup, and deployment bootstrap behavior more tolerant of real project structures and environment naming conventions.

This release strengthens the bridge from older Lex/generic-app projects into the v2 backend model.

This release improves packaging, dependency, container, or runtime configuration reliability.

Changelog

Added

  • Additional setup and initialization support for project bootstrap and environment-specific configuration.
  • Compatibility support for older project structures or legacy data where applicable.

Changed

  • Initialization behavior is more tolerant of project-specific client names, deployment targets, and generated run configuration.
  • Migration behavior is better aligned with the v2 project structure and ETL model conventions.
  • Packaging, dependency, image, or runtime defaults were adjusted for more reliable installation and deployment.

Fixed

  • 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

  • Teams moving from v1/generic-app patterns get a safer path to adopt v2 without losing operational history.

Maintenance

  • Refreshed packaged interface assets inside the backend distribution.
  • No confirmed backend behavior change is introduced by this release.

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.