chore: version packages (alpha)

[mobeenabdullah]

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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

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

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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@0.0.2-alpha.24

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.