Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/email-verify-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Clean re-application of #34's email-verification backend onto current
main, avoiding the stale-branch conflict and the stray committed binary that blocked #34. Supersedes #34 (close it once this merges).Contents
verify.go/verify_test.go— copied verbatim fromfeat/email-verification(verify-token store,GET /v1/verify,POST /v1/verify/resend,sendVerification).accounts.go—account.Verifiedfield;accountsAPIgainsverifies+requireVerify; register/resend/verify routes wired; register returns202 {status:"verify_sent"}(no session) when required, else201 {token}as today; login returns403 {reason:"unverified"}when required and unverified. The #33/#36 funnelrecordEvent("register")is preserved (moved just above the new branch so account-creation is still recorded in both paths).main.go— one-time grandfather backfill (marker-file guarded) marking pre-existing accounts verified, so enabling the gate never locks out a current customer..gitignore— ignore the/cairn-license-serverbuild artifact (root cause of #34's stray binary).Dormant by default
Everything is behind
REQUIRE_EMAIL_VERIFICATION(default off): register still returns a token and login is ungated exactly as today until the flag is set.Routing (confirmed)
publicOrigin()→ defaulthttps://license.swisscairn.ch(the/v1/verifyendpoint). ✓siteURL→https://www.swisscairn.ch/enter.html#verified(where the companionenter.html, already merged in cairn-site, handles it). ✓go vet+ fullgo test ./...(incl.TestEmailVerificationFlow) + amd64 build all green in the port workflow.