Repository navigation
chore: version packages - #15
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 31, 2026 12:45
4ddb190 to
8d8750c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 31, 2026 12:47
8d8750c to
9a25fd3
Compare
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.
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
@seamless-auth/messaging-aws@0.3.0
Minor Changes
12fff84: Email messages can carry custom headers, such as
List-UnsubscribeandList-Unsubscribe-Postfor one-click unsubscribe. Header names and values are validated so a caller cannot inject further headers, and the headers the transport sets from the message itself (From, To, Subject) are refused.The AWS email transport now sends through SES v2 (
@aws-sdk/client-sesv2), since the v1 SendEmail call cannot carry custom headers. The IAM action is stillses:SendEmail. AsesClientpassed in config must now be an SES v2 client, or anything that accepts the v2SendEmailCommand.Patch Changes
@seamless-auth/messaging@0.3.0
Minor Changes
12fff84: Email messages can carry custom headers, such as
List-UnsubscribeandList-Unsubscribe-Postfor one-click unsubscribe. Header names and values are validated so a caller cannot inject further headers, and the headers the transport sets from the message itself (From, To, Subject) are refused.The AWS email transport now sends through SES v2 (
@aws-sdk/client-sesv2), since the v1 SendEmail call cannot carry custom headers. The IAM action is stillses:SendEmail. AsesClientpassed in config must now be an SES v2 client, or anything that accepts the v2SendEmailCommand.68daa76: The message data shapes (
MessagingChannel,DeliveryResult,EmailMessage,SmsMessage,SendOtpEmailInput,SendOtpSmsInputandSendMagicLinkEmailInput) now come from@seamless-auth/types, the same definitions the auth API and server adapters use.AuthDeliveryInstruction, the delivery payload the API returns when the adopter owns delivery, is now exported too. The shapes are unchanged, and@seamless-auth/typesis only referenced by the type declarations, so nothing new loads at runtime.@seamless-auth/messaging-twilio@0.3.0
Patch Changes