chore: update version and changelog - #323
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 15, 2026 22:39
de3d009 to
4fd9f60
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 publish to npm yourself or setup this action to publish 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-api@0.14.1
Patch Changes
b092487: A decoy continuation under external delivery no longer hands the SDK a message to send.
When an adopter runs external delivery, the decoy responders for an OTP send and a magic
link request answered with a
deliveryblock like a real account's, addressed to thedecoy's synthetic
@example.invalidemail. The SDK mailed it, the domain never resolves,and the adopter's mail provider retried for hours and then bounced it against the
adopter's sending identity. Every sign-in attempt for an unknown address was a guaranteed
bounce, fourteen hours later, on traffic the adopter does not control (A decoy continuation under external delivery mails a real message to
@example.invalid, and every one bounces #321).The responders now omit the block. It is only readable by a caller holding a service
token, so a stranger sees the same answer as before, and the SDK's
deliverAuthMessagealready sends nothing when the block is absent.
decoyOtpForhad no other reason toexist and is removed.
docs/security-posture.mdsays why parity at the SDK's edge wasnot worth a bounce per probe.