105b50a277
* 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>
1.7 KiB
1.7 KiB
GitHub Actions 说明
API：Docker Build and Deploy
- 工作流文件： docker-build-deploy.yml
- 测试 job：在构建镜像前于
api/下执行uv sync --dev与pytest。 - Secrets：预发无前缀
SSH_*/DEPLOY_PATH、生产PROD_*、镜像ALIYUN_CR_*— 详见 SETUP.md。 - 分支 / Tag：
main→ Staging 服务器；语义化 tagv*.*.*→ Production 服务器；路径过滤为api/**与本 workflow。 - 手动补跑：
workflow_dispatch仅支持main/master（Staging）或vMAJOR.MINOR.PATCHtag（Production）。其它 ref 会在测试与构建前失败。
头部注释与 docker-build-deploy.yml 内说明为最新权威描述。
Android Release
构建签名 APK：见本文件历史版本中 Android 小节或仓库内 app 模块文档（若已迁移）。
App Expo Deploy
- 工作流文件：app-expo-deploy.yml
- 自动触发：
main→stage，use-env staging（app-expo/env/staging→.env）构建 APK artifact；v*.*.*tag →prod，env/production并创建 GitHub Release。 - 手动触发：
dev可用于内部测试包；stage只允许在main/master上补跑；prod需要选择vMAJOR.MINOR.PATCHtag，或在main/master上填写语义化version。 - 产物规则：Staging APK 仅上传为 GitHub Actions artifact；Production APK 才创建正式 GitHub Release。
- 版本号：CI 在 prebuild / Gradle 前注入
APP_VERSION（tag 或package.json）与APP_BUILD_NUMBER（GITHUB_RUN_NUMBER）；app.config.ts与 About 页读取同一来源，无需手改app.config.ts里的version。