docs(batch): document tags support

[cpenned]

Summary

The batch send API supports tags per email. This PR documents that support in the Ruby SDK.

Changes

• Document that each batch email supports tags
• Add a spec verifying tags are serialized in the request body

Notes

No runtime code changes were required — Resend::Batch.send forwards the params array as JSON via Resend::Request.

  

---

Summary by cubic

Documents per‑email tags support in Resend::Batch.send, noting each email accepts the same fields as Resend::Emails.send. Adds a spec to verify tags are serialized in the request body; no runtime changes.

^{Written for commit b4884ef. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Documents per-email fields (scheduled_at, tags, attachments) in batch.send method and adds a spec to verify serialization. No runtime code changes.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 2 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

Dismissed because Cubic found issues in a newer review.

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="lib/resend/batch.rb">

<violation number="1" location="lib/resend/batch.rb:10">
P2: The docstring says "Each hash accepts the same fields as {Resend::Emails.send}, including:" but according to the Resend API docs, `attachments` and `scheduled_at` are explicitly **not supported** on the batch endpoint (`POST /emails/batch`). Saying "same fields" without the exception is misleading — users who read this will pass `attachments` or `scheduled_at` parameters and silently fail or get an error at runtime. The previous version (before this PR) had no field-level documentation, which was incomplete but not actively misleading. Recommend restoring the caveat that `attachments` and `scheduled_at` are not supported in batch, e.g. "Each hash accepts the same fields as {Resend::Emails.send}, including +tags+ per email, except +scheduled_at+ and +attachments+ which are not supported in batch."</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The docstring says "Each hash accepts the same fields as {Resend::Emails.send}, including:" but according to the Resend API docs, attachments and scheduled_at are explicitly not supported on the batch endpoint (POST /emails/batch). Saying "same fields" without the exception is misleading — users who read this will pass attachments or scheduled_at parameters and silently fail or get an error at runtime. The previous version (before this PR) had no field-level documentation, which was incomplete but not actively misleading. Recommend restoring the caveat that attachments and scheduled_at are not supported in batch, e.g. "Each hash accepts the same fields as {Resend::Emails.send}, including +tags+ per email, except +scheduled_at+ and +attachments+ which are not supported in batch."

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At lib/resend/batch.rb, line 10:

<comment>The docstring says "Each hash accepts the same fields as {Resend::Emails.send}, including:" but according to the Resend API docs, `attachments` and `scheduled_at` are explicitly **not supported** on the batch endpoint (`POST /emails/batch`). Saying "same fields" without the exception is misleading — users who read this will pass `attachments` or `scheduled_at` parameters and silently fail or get an error at runtime. The previous version (before this PR) had no field-level documentation, which was incomplete but not actively misleading. Recommend restoring the caveat that `attachments` and `scheduled_at` are not supported in batch, e.g. "Each hash accepts the same fields as {Resend::Emails.send}, including +tags+ per email, except +scheduled_at+ and +attachments+ which are not supported in batch."</comment>

<file context>
@@ -7,11 +7,10 @@ class << self
       # Each email in +params+ accepts the same fields as {Resend::Emails.send},
-      # except +scheduled_at+ and +attachments+, which are not supported in batch.
-      # +tags+ are supported per email.
+      # including +tags+ per email.
       #
       # @param params [Array<Hash>] Array of email parameters (max 100 emails).
</file context>