Lex App v2.0.0rc20
Lex App v2.0.0rc20
Release Notes
This release improves backend support for Streamlit dashboards served through Lex App.
Project teams can rely on a smoother dashboard path for analytics/reporting models without treating Streamlit as a separate operational exception.
This release reduces setup and initialization friction for Lex App projects.
This release strengthens the bridge from older Lex/generic-app projects into the v2 backend model.
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
- Streamlit dashboard serving is better aligned with backend routing, proxying, and session expectations.
- 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.
Fixed
- Reduced embedded dashboard startup, layout, and token/context handling problems.
- 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
- Report models that expose Streamlit dashboards are easier to run in local and deployed environments.
- Teams moving from v1/generic-app patterns get a safer path to adopt v2 without losing operational history.
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.
- Restart the Streamlit-serving backend process where dashboards are hosted through Lex App.
- 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.
