fix(mailer): include SiteURL in notification template data#2532
Merged
cstockton merged 3 commits intoMay 26, 2026
Merged
Conversation
The seven notification mail builders (PasswordChanged, EmailChanged,
PhoneChanged, IdentityLinked, IdentityUnlinked, MFAFactorEnrolled,
MFAFactorUnenrolled) omitted SiteURL from their template data maps,
so templates referencing {{ .SiteURL }} rendered an empty string at
runtime. The standard mail builders (Invite, Confirmation, Recovery,
MagicLink, EmailChange, Reauthentication) already include it, and
checkDefaults whitelists SiteURL for all template types, so this was
an oversight rather than an intentional restriction.
Closes supabase#2468
|
@jeffreywescott - ty for hopping in... someone else has dropped in, but they were ignored - i just hope that the same does not happens with you, because i'm tired of "hacking" for things to work (and not all the hacks work as expected, and this is draining me up!) |
Contributor
|
@jeffreywescott @vonschappler Thanks for taking the time to point this out and apologies for the delay, I'll get this merged soon as the tests pass. |
cstockton
pushed a commit
to supabase/supabase
that referenced
this pull request
May 26, 2026
This will make email templates more consistent and may be merged after supabase/auth#2532 is deployed.
Contributor
|
This will be available to use inside templates immediately after the next auth release. However it will not show up in the dashboard template editor until supabase/supabase#46393 is merged, which must be done after the auth release. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The seven notification mail builders (
PasswordChanged,EmailChanged,PhoneChanged,IdentityLinked,IdentityUnlinked,MFAFactorEnrolled,MFAFactorUnenrolled) omittedSiteURLfrom their template data maps, so templates referencing{{ .SiteURL }}render an empty string at runtime. The standard mail builders (Invite,Confirmation,Recovery,MagicLink,EmailChange,Reauthentication) already include it, andcheckDefaultsintemplate.goalready whitelistsSiteURLfor all template types — so this looks like an oversight from when notification templates were added, not an intentional restriction.Closes #2468
Test plan
go build ./...passesgo test ./internal/mailer/templatemailer/...passesgofmtclean