* feat(api): implement Google OAuth login and user management
- Added Google OpenID Connect login functionality, allowing users to authenticate using their Google accounts.
- Created new endpoints for Google login, including user registration and linking existing accounts.
- Introduced Google token verification logic and error handling for authentication failures.
- Updated environment configuration to include Google OAuth client IDs and verification settings.
- Enhanced user model to support OpenID and linked Google accounts.
This feature improves user experience by enabling seamless sign-in with Google, while maintaining security and integrity of user data.
* fix(auth): wire staging Google token verifier
* chore(deps): update expo to version 55.0.6 and adjust @expo/env dependency in pnpm-lock.yaml
* chore(deps): update Babel dependencies to version 7.29.7 in package-lock.json
* feat(auth): enhance phone login for China users
- Updated phone login functionality to support only mainland China (+86) mobile numbers.
- Added user prompts and descriptions for phone login, including confirmation and cancellation options.
- Adjusted translations for both English and Chinese to reflect the new phone login requirements.
- Updated Google OAuth client IDs in configuration files for production and staging environments.
* chore(deps): add peer flag to use-sync-external-store in package-lock.json
* chore(deps): add @emnapi/core and @emnapi/runtime to package-lock.json
* fix(app-expo): align Android native dependencies
* fix(app-expo): normalize lockfile for npm 10
* fix(config): update environment variable handling to use static access
- Introduced a static mapping for public environment variables to ensure proper access during the release bundle.
- Updated the `requirePublicEnv` and `optionalPublicEnv` functions to reference the new `PUBLIC_ENV` object instead of directly accessing `process.env`.
- Added comments to clarify the necessity of static access for certain environment variables.
* feat(app-expo): dark mode, FAQ i18n, eval ASR, and theme cleanup (#34)
* feat(app-expo): dark mode, FAQ i18n, version CI, and theme cleanup
Implement light/dark scene colors across chat, reading, and headers; remove
default/brand theme picker and ThemeVariablesProvider. Localize FAQ in-app,
fix dark-mode text visibility, and remove the unused /api/faqs endpoint.
Align About/version with Expo config and inject APP_VERSION in CI builds.
Also includes phone E164 auth/SMS updates, eval ASR page, and related API work.
* revert: remove phone E.164 changes from dark-mode branch
These auth/SMS internationalization updates were accidentally bundled into
the dark-mode commit; restore 11-digit CN phone flow and drop related API,
migration, and Expo UI work from this branch.
* fix: address PR review issues for dark mode and eval ASR
Use light foreground colors for sepia reading in dark mode, fix chat send
button contrast, stream-limit eval ASR uploads, restore LiveTester phone
validation, and remove unused AudioSegmenter code.
* fix(app-expo): improve chat send button contrast in light and dark mode
Add dedicated send button colors (accent fill in dark, primary fill in
light), use RNText to avoid NativeWind overrides, and restore dark labels
in light mode for readable composer actions.
---------
Co-authored-by: Kevin <kevin@brighteng.org>
---------
Co-authored-by: penghanyuan <penghanyuan@gmail.com>
Co-authored-by: Kevin <kevin@brighteng.org>
This commit changes the revision identifier from '0020_backfill_all_missing_columns' to '0020_backfill_missing_schema' to better reflect the purpose of the migration, which focuses on backfilling missing schema elements in the database.
This migration updates the database schema by automatically adding all missing columns from the ORM models to the existing tables. It replaces the previous specific addition of 'tts_audio_urls' with a more comprehensive approach that inspects the ORM metadata and synchronizes it with the database schema. The downgrade function has been simplified to a no-op.
This migration introduces the 'tts_audio_urls' column to both the 'segments' and 'conversation_messages' tables, addressing a discrepancy between the ORM model and the production database. The upgrade function checks for the existence of these columns and adds them if they are missing, while the downgrade function allows for their removal if necessary.
This migration adds the columns 'audio_duration_seconds' to the 'segments' table and 'deleted_at' to the 'conversations' table, which were previously missing in the production database. The upgrade function checks for the existence of these columns and adds them if they are not present. The downgrade function allows for the removal of these columns if necessary.
