resend-cli 2.9.0 → 2.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "resend-cli",
-  "version": "2.9.0",
+  "version": "2.11.0",
   "description": "The official CLI for Resend",
   "license": "MIT",
   "repository": {
@@ -46,7 +46,7 @@
     "esbuild": "0.28.1",
     "esbuild-wasm": "0.28.0",
     "picocolors": "1.1.1",
-    "resend": "6.18.0-canary.0"
+    "resend": "6.18.1"
   },
   "pkg": {
     "scripts": [

package/skills/resend-cli/SKILL.md

@@ -13,7 +13,7 @@ metadata:
   author: resend
   # Skill version is independent from the CLI/package.json version —
   # bump it on skill content changes, not CLI releases.
-  version: "2.4.0"
+  version: "2.6.0"
   homepage: https://resend.com/docs/cli-agents
   source: https://github.com/resend/resend-cli
   openclaw:
@@ -169,12 +169,13 @@ Read the matching reference file for detailed flags and output shapes.
 | 1 | **Forgetting `--yes` on delete commands** | All `delete`/`rm` subcommands require `--yes` in non-interactive mode — otherwise the CLI exits with an error |
 | 2 | **Not saving webhook `signing_secret`** | `webhooks create` shows the secret once only — it cannot be retrieved later. Capture it from command output immediately |
 | 3 | **Omitting `--quiet` in CI** | Without `-q`, spinners and status text still go to stderr (not stdout). Use `-q` for JSON on stdout with no spinner noise on stderr |
-| 4 | **Using `--scheduled-at` with batch** | Batch sending does not support `scheduled_at` — use single `emails send` instead |
+| 4 | **Passing `--scheduled-at` as a flag to batch** | There is no `--scheduled-at` flag on `emails batch` — set `scheduled_at` per-email in the JSON file instead |
 | 5 | **Expecting `domains list` to include DNS records** | List returns summaries only — use `domains get <id>` for the full `records[]` array |
 | 6 | **Sending a dashboard-created broadcast via CLI** | Only API-created broadcasts can be sent with `broadcasts send` — dashboard broadcasts must be sent from the dashboard |
 | 7 | **Passing `--events` to `webhooks update` expecting additive behavior** | `--events` replaces the entire subscription list — always pass the complete set |
 | 8 | **Expecting `logs list` to include request/response bodies** | List returns summary fields only — use `logs get <id>` for full `request_body` and `response_body` |
 | 9 | **CSV import fails with `create_error` ("missing required email column")** | `contacts imports create` matches columns case-sensitively by lowercase names (`email`, `first_name`, `last_name`) — use `--column-map` for headers like `Email`/`First Name` |
+| 10 | **URL attachment "succeeds" but the email never arrives** | The API fetches `--attachment "https://..."` URLs after returning the email ID — an unreachable URL fails the email asynchronously. Verify with `emails get <id>` (`last_event: "failed"`), and always pass `;filename=` and `;type=` since neither is derived from the URL (defaults: `attachment-0`, `application/octet-stream`) |
 
 ## Common Patterns
 
@@ -183,6 +184,11 @@ Read the matching reference file for detailed flags and output shapes.
 resend emails send --from "you@domain.com" --to user@example.com --subject "Hello" --text "Body"
 ```
 
+**Send an inline image (CID attachment) — always double-quote `;` params (required on bash, PowerShell, and cmd):**
+```bash
+resend emails send --from "you@domain.com" --to user@example.com --subject "Hello" --html "<img src=cid:logo>" --attachment "./logo.png;cid=logo"
+```
+
 **Send a React Email template (.tsx):**
 ```bash
 resend emails send --from "you@domain.com" --to user@example.com --subject "Welcome" --react-email ./emails/welcome.tsx

package/skills/resend-cli/references/domains.md

@@ -28,6 +28,7 @@ Create a new domain and receive DNS records to configure.
 | `--region <region>` | string | No | `us-east-1` \| `eu-west-1` \| `sa-east-1` \| `ap-northeast-1` |
 | `--tls <mode>` | string | No | `opportunistic` (default) \| `enforced` |
 | `--tracking-subdomain <subdomain>` | string | No | Subdomain for click and open tracking (e.g., `track`) |
+| `--custom-return-path <subdomain>` | string | No | Subdomain for the Return-Path address (e.g., `bounce`) |
 | `--sending` | boolean | No | Enable sending (default: enabled) |
 | `--receiving` | boolean | No | Enable receiving (default: disabled) |
 

package/skills/resend-cli/references/emails.md

@@ -24,11 +24,27 @@ Send an email via the Resend API.
 | `--bcc <addresses...>` | string[] | No | BCC recipients |
 | `--reply-to <address>` | string | No | Reply-to address |
 | `--scheduled-at <datetime>` | string | No | Schedule for later — ISO 8601 or natural language (e.g. `"in 1 hour"`, `"tomorrow at 9am ET"`) |
-| `--attachment <paths...>` | string[] | No | File paths to attach (not compatible with `--template`) |
+| `--attachment <specs...>` | string[] | No | File path or `https://` URL to attach, with optional `;cid=`, `;type=`, `;filename=` params (not compatible with `--template`) |
+| `--attachments-file <path>` | string | No | Path to a JSON array of attachment objects (`"-"` for stdin; not compatible with `--template`) |
 | `--headers <key=value...>` | string[] | No | Custom headers |
 | `--tags <name=value...>` | string[] | No | Email tags |
 | `--idempotency-key <key>` | string | No | Deduplicate request |
 
+**Attachment syntax:** append `;cid=<id>` (inline content-id referenced as `cid:` in HTML), `;type=<mime>`, and/or `;filename=<name>` to the path or URL. ALWAYS double-quote values containing `;` — single quotes break on Windows cmd, and unquoted `;` breaks on every shell:
+
+```bash
+resend emails send ... --html "<img src=cid:logo>" --attachment "./logo.png;cid=logo"
+resend emails send ... --attachment "https://example.com/report.pdf;type=application/pdf"
+```
+
+For paths containing a literal `;key=` or for scripted use, pass `--attachments-file` with a JSON array of objects with `content` (base64) or `path` (URL), plus optional `filename`, `content_type`, `content_id` (camelCase also accepted).
+
+**URL attachment caveats:** the API fetches the URL *after* the send request returns an email ID — an unreachable URL fails the email asynchronously (`last_event: "failed"` on `emails get <id>`). Filename and MIME type are NOT derived from the URL (stored as `attachment-0` / `application/octet-stream`), so pass `;filename=` and `;type=` with every URL attachment:
+
+```bash
+resend emails send ... --attachment "https://example.com/report.pdf;filename=report.pdf;type=application/pdf"
+```
+
 **Output:** `{"id":"<uuid>"}`
 
 ---
@@ -49,7 +65,7 @@ Retrieve a sent email by ID.
   "to": ["user@example.com"],
   "subject": "Hello",
   "last_event": "delivered",
-  "created_at": "<iso-date>",
+  "created_at": "<date>",
   "scheduled_at": null
 }
 ```
@@ -85,14 +101,16 @@ Send up to 100 emails in a single request.
 ```json
 [
   {"from":"a@domain.com","to":["b@example.com"],"subject":"Hi","text":"Body"},
-  {"from":"a@domain.com","to":["c@example.com"],"subject":"Hi","html":"<b>Body</b>"}
+  {"from":"a@domain.com","to":["c@example.com"],"subject":"Hi","html":"<b>Body</b>","scheduled_at":"in 1 hour","tags":[{"name":"campaign","value":"welcome"}]}
 ]
 ```
 
+Per-email `scheduled_at` (ISO 8601 or natural language) and `tags` are supported.
+
 **Output (success):** `[{"id":"..."},{"id":"..."}]`
 **Output (permissive with errors):** `{"data":[{"id":"..."}],"errors":[{"index":1,"message":"..."}]}`
 
-**Constraints:** Max 100 emails. Attachments and `scheduled_at` not supported per-email.
+**Constraints:** Max 100 emails. Attachments not supported per-email.
 
 ---