Vercel marketplace deployment trigger fixed
Initial deployments now trigger correctly for Vercel marketplace flows by persisting marketplace context through the onboarding journey instead of relying on redirect URLs.
The Vercel marketplace integration was not triggering initial deployments after users connected GitHub. The original implementation checked the redirect URL for marketplace context, but this context was lost during the GitHub App installation redirect cycle — when users install the GitHub App for the first time, the full-page redirect causes the marketplace origin to be forgotten.
The fix persists the marketplace origin directly on the Vercel integration as onboardingOrigin ("marketplace" or "dashboard") when the onboarding starts. This value survives the GitHub App installation redirect and is checked when the GitHub connection completes to determine whether to trigger the initial deployment.
Additionally, the email login option is now hidden on the login page when users arrive from the Vercel marketplace, reducing friction in the onboarding flow. In the Vercel onboarding modal, users who completed onboarding but haven't connected GitHub are now routed directly to the GitHub connection step.
This fix is in the webapp's Vercel onboarding and integration services.