prepare for release v0.7.0 - #207
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Coverage Report for CI Build 29753214145Coverage remained the same at 57.272%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
ePDS@0.7.0
Who should read this release
Minor Changes
#197
ce25bebThanks @aspiers! - Email delivery logs use a consistent recipient field.Affects: Operators
Operators: All four email delivery paths now log the recipient as
email: client-branded OTP, standard sign-in OTP, welcome OTP, and backup-email verification. Update structured-log queries forSent client-branded OTP emailto reademailinstead ofto.#203
2193515Thanks @aspiers! - OTP send logs now record how long the email handoff took, the provider's message ID, and the SMTP server response.Affects: Operators
Operators: every OTP email completion line (all four paths — client-branded, sign-in, welcome, backup-email verification) now carries
elapsedMs,messageId, andsmtpResponsealongsideemail.messageIdlets these logs be joined to Resend delivery events;elapsedMsisolates a slow SMTP handoff from other causes of late-arriving codes. Failed sends logelapsedMstoo, on the existingbetter-auth: failed to send OTP emailerror line.#198
2bf9af4Thanks @aspiers! - Optional email-event logging for operators who choose the third-party Resend service to send email; ePDS continues to support other email providers.Affects: Operators
Operators: ePDS remains compatible with any SMTP provider and does not require Resend. Operators who already use Resend can opt in by registering
https://<AUTH_HOSTNAME>/webhooks/resendfor the documented email events and settingRESEND_WEBHOOK_SECRET; logs include delivery, open, complaint, suppression, and scheduling events. The route verifies each webhook, logs only events whose sender exactly matchesSMTP_FROM, acknowledges unsupported click and inbound events without logging their payloads, and does not persist webhook data.