Auto email reminder for membership renewal

[ErikaKK]

Change Summary

[Briefly summarise the changes that you made. Just high-level stuff]

• Cron jobs tested.
• Resend can only send 100 emails per day so I set 4 reminder job assuming we will have 300-400 members:)
• Added a column in user table

Change Form

Fill this up (NA if not available). If a certain criteria is not met, can you please give a reason.

• The pull request title has an issue number
• The change works by "Smoke testing" or quick testing
• The change has tests
• The change has documentation

Other Information

[Is there anything in particular in the review that I should be aware of?]

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 2, 2025 11:05am

[Julie-Salazar]

how is the cron key handled :0 would it fail if the env variables aren't defined here? not entirely sure since i haven't done something like this before

[ErikaKK]

It's defined in vercel env variables

[Julie-Salazar]

this looks really good 👍

[Julie-Salazar]

hmm publishing the schema shouldn't be sus i think... so ye looks ok, we just need to be safe about other sensitive data

[Julie-Salazar]

Looks good!!
We currently have like 400ish rows on db, could do only updating reminder_pending to false after successful email send and this might make it easier to keep track of resend

[ErikaKK]

Looks good!! We currently have like 400ish rows on db, could do only updating reminder_pending to false after successful email send and this might make it easier to keep track of resend

That is a good point. Thank you!