-
-
Notifications
You must be signed in to change notification settings - Fork 774
fix(api): send verification email upon public status page email subscription (#2571) #2588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Rodrigoue9
wants to merge
9
commits into
openstatusHQ:main
Choose a base branch
from
Rodrigoue9:fix/bounty-2571
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
615b8c3
fix(api): send verification email upon public status page email subsc…
Rodrigoue9 9b8d105
feat: complete delivery and test suite
Rodrigoue9 fa8812a
fix(api): prevent duplicate verification emails with rate-limiting & …
Rodrigoue9 58c17d6
fix(api): atomic concurrency lock and deduplication for verification …
Rodrigoue9 ab49651
ci: apply automated fixes
autofix-ci[bot] 393f02f
fix(status-page): send subscription verification only once
Rodrigoue9 c192a22
fix(status-page): validate subscription email flow
Rodrigoue9 7a45725
fix(status-page): handle verification email send failure and cleanup …
Rodrigoue9 678ffbb
fix(status-page): restrict send-failure cleanup to pending unaccepted…
Rodrigoue9 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P1: A visitor now receives two subscription confirmation emails. This PR sends the verification email directly in
statusPage.subscribe, but the status-page frontend (header.tsx) still callsemailRouter.sendPageSubscriptionVerificationin the subscribe mutation'sonSuccess, and that procedure also resends the same verification email for the same subscriber/token. SincesendPageSubscriptiondoesn't set a Resend idempotency key, both emails are delivered. Inline the server-side send here and drop the frontend follow-up call (or the reverse), so only one email is sent.Prompt for AI agents