Port cron-minutely fixes: reactivate tombstoned subs + confirm-email rate limit #29
Loading…
Reference in a new issue
No description provided.
Delete branch "mailship-fc-merge-cron-fixes-df6"
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?
Port of the three genuine commits from origin/cron-minutely onto main. Skipped commits are already on main, superseded, or deliberate:
291f92c"Run cron every minute for testing" — testing hack, excluded on purpose.395b192"Set trust proxy..." — byte-identical to mains8235513(same patch-id).ce59c15"dedupe and serialize subscription writes" — superseded: main already carries the partial unique-index migration + insert race fallback.082b442"Update subscription confirmation email template" +cdabec2"log errors" — content already on main (branded template, normalized EVENT_VIEWER_URL).Included:
fd81528"Re-activate tombstoned subscriptions when email is the same"5675ebd"fix reactivating old rows"051c1e8"Rate-limit confirmation emails and restore daily/weekly digest cron" — confirm-email cooldown (10 min) merged with mains schedule-aware upsert: email-change branch resets last_confirm_sent_at, Subscription type gains the field; the cron "restore" part is a no-op against mains schedule-aware getCronExpression.Verified: tsc --noEmit, eslint src, vitest run (13 files / 57 tests) all pass.