Lex App v2.0.0rc53
Lex App v2.0.0rc53
Release Notes
This release hardens identity, token, and permission handling across backend request paths.
For business applications with role-aware data, the main value is more consistent user context and permission behavior between interactive use, API access, and embedded dashboard flows.
This release improves backend support for Streamlit dashboards served through Lex App.
This release reduces setup and initialization friction for Lex App projects.
Changelog
Added
- Additional setup and initialization support for project bootstrap and environment-specific configuration.
Changed
- Token, session, and permission context handling is more consistent across backend request types.
- 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.
Fixed
- Reduced authentication edge cases around Keycloak, API tokens, role/group lookup, and user-context enrichment.
- 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.
Improved
- Permission-aware behavior is more predictable for role-based business applications.
- Report models that expose Streamlit dashboards are easier to run in local and deployed environments.
Maintenance
- Kept the distributable backend package aligned with the current v2 runtime expectations.
Upgrade Impact
- Verify Keycloak, token, group, and role configuration in each environment after deployment.
- 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.
