Release v0.2.1#3
Merged
Merged
Conversation
Reject unsubscribe, webhook, and send requests with a server error when their HMAC, webhook, or Resend secrets are missing, instead of operating under an empty key.
Move SendMessage and SendResult into the shared kit/email types and re-export them so consumers type their EMAIL service binding against the published contract; the email Worker re-exports them for its own use.
Patch release: send() RPC contract export and email secret fail-closed guards.
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
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.
Two additive changes:
send()paths now reject with a server error when their HMAC, webhook, or Resend secrets are missing, instead of operating under an empty key.send()RPC contract from@ampl/kit/email.SendMessageandSendResultnow live in the sharedkit/emailtypes and are re-exported, so consumers type theirEMAILservice binding against the published contract instead of vendoring it.No schema changes. Consumers on v0.2.0 are unaffected (additive).