Conversation
* feat(stripe): add Stripe integration with auto-approval for internal team * chore: merge main into it * fix(upgrade): harden stripe domain auto-approval * chore(posthog): update getPostHogClient to return a Promise and await client calls * refactor(posthog): simplify client calls by removing async/await * fix(stripe): require exact domain match for customer lookup --------- Co-authored-by: Mariano Fuentes <marfuen98@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryAdds Stripe-based domain checks to auto-approve org access and an internal-only onboarding fast-path, with env and dependency updates. Stripe-backed domain auto-approval and internal onboarding fast-path
Written by Cursor Bugbot for commit da9bab9. This will update automatically on new commits. Configure here. |
|
|
Graphite Automations"Auto-assign PRs to Author" took an action on this PR • (12/22/25)1 reviewer was added to this PR based on Mariano Fuentes's automation. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| const canSkipOnboarding = useMemo(() => { | ||
| if (!userEmail) return false; | ||
| return userEmail.endsWith('@trycomp.ai'); | ||
| }, [userEmail]); |
There was a problem hiding this comment.
Case-sensitive mismatch in internal team email checks
The canSkipOnboarding check uses userEmail.endsWith('@trycomp.ai') which is case-sensitive, while the upgrade page's isTrycompEmail check uses extractDomain which lowercases the email domain before comparison. For an email like User@TryComp.AI, the upgrade page would auto-approve the organization (domain becomes trycomp.ai), but the onboarding page would not show the skip button (case-sensitive endsWith fails). This creates inconsistent behavior for the same internal team feature.
Additional Locations (1)
|
🎉 This PR is included in version 1.72.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 participants
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.