fix(tooling): recognize Resend Forge DNS - #66
Merged
Merged
Conversation
Production preflight now checks the records Resend issues for new sending domains. Existing SES manifests keep their current checks. Teams can switch profiles when their domain uses Forge. Co-authored-by: Codex <noreply@openai.com>
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.
TL;DR
Production checks can recognize the DNS records Resend currently issues for lvwwd.org.
Overview of Changes
Resend's current sending setup uses
rsendandsendCNAMEs plus a DKIM TXT record. Add an explicitforgeDNS profile to the platform manifest and check those records against their expected targets. Keep the existing SES MX and SPF checks as the default so current repositories remain compatible. Update setup guidance and tests for both profiles.The public DNS records for lvwwd.org resolve as expected, and
pnpm checkpasses (272 CLI tests and 79 web platform tests). DNS checks alone do not prove a message can be delivered.Follow-ups
Prove a real signup and link-recovery email from the live site before partner promotion.