mctxchangelog

Streamlined Onboarding & Email Verification

February 14, 2026 • 2026-02-14.001

This release streamlines the developer onboarding experience and adds email verification to ensure subscribers can reach you when they need help.

Features

  • Support email verification now required before deployment — verify via 6-digit code or click-to-verify link sent to your email
  • Consolidated GitHub connection step combines OAuth and repository access into one streamlined flow
  • 5-step onboarding replaces the previous 6-step flow for faster time-to-deploy
  • Shared onboarding components provide consistent experience between checklist and settings pages
  • Deploy and Publish actions are gated until email verification is complete, preventing deployment with unverified contact information
  • Email verification status persists across sessions and automatically unlocks deployment when completed

Improvements

  • GitHub connection step now covers both account linking and repository installation in a single action
  • Onboarding checklist reflects actual developer journey: Connect GitHub → Create Server → Add Support Email → Set Up Payouts → Deploy & Publish
  • Support email settings show clear verification state with actionable next steps
  • Backend enforces email verification requirement with 403 responses, ensuring verification cannot be bypassed

What This Means for You

New developers: Your onboarding is faster with one fewer step. GitHub connection now handles both account linking and repository access together.

Existing developers: If you haven't verified your support email yet, you'll need to verify it before your next deployment. Check your settings page for the verification prompt.

All developers: Verified support emails ensure subscribers can reach you, reducing support friction and improving the subscriber experience.

Ready to deploy? Make sure your support email is verified in settings, then deploy with confidence knowing subscribers can contact you.