Skip to content

v0.0.2-alpha.24

Pre-release
Pre-release

Choose a tag to compare

View all tags
@mobeenabdullah mobeenabdullah released this 17 Jun 11:24
· 9 commits to main since this release
v0.0.2-alpha.24
1b5ae51
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Released all 12 packages at 0.0.2-alpha.24 in lockstep (nextly, create-nextly-app, and 10 @nextlyhq/* packages).

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

@nextlyhq/adapter-mysql

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/adapter-drizzle@0.0.2-alpha.24

@nextlyhq/adapter-postgres

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/adapter-drizzle@0.0.2-alpha.24

@nextlyhq/adapter-sqlite

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/adapter-drizzle@0.0.2-alpha.24

@nextlyhq/admin

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/ui@0.0.2-alpha.24

create-nextly-app

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

nextly

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/adapter-drizzle@0.0.2-alpha.24
    • @nextlyhq/adapter-mysql@0.0.2-alpha.24
    • @nextlyhq/adapter-postgres@0.0.2-alpha.24
    • @nextlyhq/adapter-sqlite@0.0.2-alpha.24

@nextlyhq/plugin-form-builder

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

  • Updated dependencies [01f3f7a]:

    • @nextlyhq/admin@0.0.2-alpha.24
    • nextly@0.0.2-alpha.24
    • @nextlyhq/ui@0.0.2-alpha.24

@nextlyhq/storage-s3

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

@nextlyhq/storage-uploadthing

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

@nextlyhq/storage-vercel-blob

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

@nextlyhq/ui

Patch Changes

  • #103 01f3f7a Thanks @faisal-rx! - Forward cc/bcc consistently across every email send path.

    nextly.email.send and nextly.email.sendWithTemplate (Direct API) now accept and forward cc/bcc — they are added to SendEmailArgs and SendTemplateEmailArgs. Previously the Direct API namespace silently dropped both fields, so only the REST route (/api/email/send-with-template) honored them. EmailService.sendWithTemplate also dropped cc/bcc on its code-first template fallback branch while the DB-template branch already forwarded them; both branches now forward them. Empty cc/bcc arrays are not forwarded, so they don't override the "no options" path.

Assets 2
Loading