Lex App v2.0.0rc107
Lex App v2.0.0rc107
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 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
- Token, session, and permission context handling is more consistent across backend request types.
- 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 authentication edge cases around Keycloak, API tokens, role/group lookup, and user-context enrichment.
- 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
- Permission-aware behavior is more predictable for role-based business applications.
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.
- 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.
