v0.6.3-beta: Migration UX & Auth Visibility Hotfix - #44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
created_by_user_id), causing raw SQL errors when saving checks.alembic upgrade headbefore using checks.Description
backend/app/core/system_status.pyby returningschema_version,migration_head,migration_statusand optionalmigration_message, and treating missingalembic_versionwith existing tables asbehindwithout raising internal exceptions.operational_warningstobuild_system_statuswhen the database schema is notup_to_dateand bumped the backend system version tov0.6.3-beta.sqlalchemy.exc.OperationalErrorinbackend/app/api/routes_checks.pyand returning a clear HTTP 503 with migration instructions when the DB is missingcreated_by_user_id.getMe()ascurrentUser, show username and role in theLayout, add a visibleLogoutbutton andlogout()API call, display migration-warning banners in Dashboard and System views, and present a friendly message when the backend indicates migrations are required.table checks has no column named created_by_user_idtodocs/operations/database-migrations.mdand appendedv0.6.3-betarelease notes; bumped versions in backend and frontend metadata.migration_statuswarnings are surfaced and that the check-store path maps the missing-column OperationalError to a migration-related HTTP 503.Testing
pytest -q backend/tests/test_api_smoke.pyand all tests passed (21 passed).npm --prefix frontend run buildand the production build completed successfully.Codex Task