fix: mobile integrations and Google Search Console OAuth - #670
fix: mobile integrations and Google Search Console OAuth#670izadoesdev wants to merge 4 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Unkey Deploy
|
Fixes the mobile MCP/integrations UI and isolates Search Console onto a dedicated Google OAuth client. Adds production readiness allow/deny flags; Search Console remains disabled in production until its OAuth app is verified and explicitly enabled. No database changes.
Summary by cubic
Fixes the integrations UI on mobile and moves Google Search Console to its own OAuth provider gated for production. Previously Search Console used the shared Google provider; now it uses
google-search-console, and in production non‑ready integrations show “Not ready,” disable actions, and skip queries.Key Changes
google-search-consoleprovider viagenericOAuthin@databuddy/auth, using constants from@databuddy/shared/integrations.INTEGRATION_PRODUCTION_READYto control production availability; non‑prod ignores this gate.@databuddy/aiand@databuddy/rpcto use the new provider ID/scope;.env.exampleaddsGOOGLE_SEARCH_CONSOLE_CLIENT_ID/GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET.Migration
GOOGLE_SEARCH_CONSOLE_CLIENT_IDandGOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, then setINTEGRATION_PRODUCTION_READY['google-search-console'] = true.Written for commit 7b4e8df. Summary will update on new commits.