Skip to content

chore: depend on @seamless-auth/messaging 0.3 - #548

Merged
Bccorb merged 2 commits into
mainfrom
chore/messaging-0-3
Nov 1, 2026
Merged

Bccorb merged 2 commits into
mainfrom
chore/messaging-0-3

Conversation

@Bccorb

@Bccorb Bccorb commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Moves @seamless-auth/messaging, @seamless-auth/messaging-aws and @seamless-auth/messaging-twilio from ^0.2.0 to ^0.3.1.

What 0.3 changes for the API:

  • The AWS email transport sends through SES v2. The API does not pass its own sesClient, so no code changes. The IAM action is still ses:SendEmail.
  • Email messages can carry validated custom headers. The API does not send any yet.
  • The message shapes now come from @seamless-auth/types (type only, nothing new at runtime).

0.3.1 (fells-code/seamless-auth-messaging#19) declares @seamless-auth/types ^0.34.0, so the lockfile now installs a single types 0.34.0 instead of a second 0.33.0 under messaging.

Not a contract change: no routes, schemas, tokens or status codes move.

Checks run locally:

  • npm run typecheck: pass
  • npm run lint: pass
  • npm run format:check: pass
  • npm run test:run: 170 files, 2741 tests pass (1 todo)
  • npm run coverage: statements 99.01, branches 95.77, functions 99.37, lines 99.23 (all above thresholds)

@Bccorb
Bccorb marked this pull request as ready for review November 1, 2026 15:02
@Bccorb
Bccorb merged commit a4ffb66 into main Nov 1, 2026
7 checks passed
@Bccorb
Bccorb deleted the chore/messaging-0-3 branch November 1, 2026 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant