QQQ 0.40 brought field functions with backend-specific implementations, OAuth2 externalBaseUrl support and fixes around joins and in-memory record handling. The notes also call out removal of SHA1 compatibility from table-based password authentication.
QQQ 0.40 brought field functions with backend-specific implementations, OAuth2 externalBaseUrl support and fixes around joins and in-memory record handling. The notes also call out removal of SHA1 compatibility from table-based password authentication.
Computed fields need a consistent meaning across storage engines. Internal and external URLs need a consistent meaning across deployment boundaries. These are different features with the same architectural demand: make the framework contract explicit. The authentication change is a migration consideration, not an incidental dependency update; existing applications should read the release notes before adopting it.
Retrospective entry assembled on October 12, 2026. The journal date records the GitHub release notes, not when this website entry was written.