@wraps.dev/cli 3.20.0 → 3.20.1

package/dist/cli.js

@@ -61962,9 +61962,7 @@ async function suppressionsRemove(options) {
       `Removed ${email} from the suppression list of account ${accountId}.`
     );
   } else {
-    log49.warn(
-      `${email} was no longer on the list of account ${accountId}; nothing changed.`
-    );
+    log49.warn(`${email} was no longer on the list of account ${accountId}.`);
   }
 }
 function addFailure(status2, text15) {
@@ -64886,7 +64884,7 @@ async function deleteFailure(resp, singleId) {
     return {
       code: "CONFLICT",
       message: `${firstText(body?.error) ?? "A broadcast or workflow still uses one of these templates."} Blocking template ids: ${blockingIds.join(", ") || "none reported"}.`,
-      suggestion: "Finish or cancel each scheduled, queued or processing broadcast that uses a blocking template (`wraps broadcasts cancel <id> --yes`), or disable each enabled workflow that sends it (`wraps workflows disable <workflow-id>`). Find the workflows with `wraps workflows list` and the broadcasts in the dashboard. Then re-run the delete. Nothing was deleted."
+      suggestion: "Point each draft broadcast that uses a blocking template at another one (`wraps broadcasts update <id> --template-id <other-id>`, or `--clear-template-id`). Finish or cancel each scheduled, queued or processing broadcast that uses one (`wraps broadcasts cancel <id> --yes`), and pause each enabled workflow in the dashboard, or, for a workflow defined in code, remove the template from its steps and run `wraps email workflows push` again (if the push reports a dashboard edit, ask the user before using `--force`, which overwrites those edits). Find the workflows with `wraps workflows list` and the broadcasts in the dashboard. Then re-run the delete. Nothing was deleted."
     };
   }
   if (resp.status === 404 && singleId !== void 0) {
@@ -64994,7 +64992,7 @@ async function templatesDelete(options) {
   if (!options.yes) {
     fail9(command6, {
       code: "CONFIRMATION_REQUIRED",
-      message: `Deleting ${ids.length} template(s) removes them and their versions. A published SES copy is removed too, unless another template still uses that name. If any template is still used by a scheduled, queued or processing broadcast, or an enabled workflow, the whole delete is refused. Nothing was deleted.`,
+      message: `Deleting ${ids.length} template(s) removes them and their versions. A published SES copy is removed too, unless another template still uses that name. If any template is still used by a draft, scheduled, queued or processing broadcast, or an enabled workflow, the whole delete is refused. Nothing was deleted.`,
       suggestion: `Preview with \`wraps email templates delete ${ids.join(" ")} --dry-run\`, then re-run with --yes.`
     });
     return;
@@ -67661,7 +67659,7 @@ defineWorkflow({
 | Type | Required Config | Description |
 |------|----------------|-------------|
 | \`contact_created\` | \u2014 | Fires when a new contact is created |
-| \`contact_updated\` | \u2014 | Fires when a contact is updated |
+| \`contact_updated\` | \u2014 | Fires on every contact update through the API or CLI (\`PATCH /v1/contacts/:id\`, \`wraps contacts update\`), when a contact is edited in the dashboard, and when its email status changes (suppressed, bounced, complained, unsubscribed, or active again after a suppression is removed). Imports (dashboard CSV, \`POST /v1/contacts/import\`, \`wraps contacts import\`) don't fire it. Event data carries \`updatedFields\` and \`changeSource\`: \`api\` (an API key), \`user\` (a signed-in user in the dashboard or CLI), \`bounce\`, \`complaint\`, \`ses_suppression\` or \`unsubscribe\` (the unsubscribe link, or the preference centre's "unsubscribe from all"). If the workflow sends email, set \`reentryDelaySeconds\` or branch on \`changeSource\`, so a bounce or unsubscribe from its own email does not start it again |
 | \`event\` | \`eventName: string\` | Fires on a custom event (e.g. \`'cart.abandoned'\`) |
 | \`segment_entry\` | \`segmentId: string\` | Fires when a contact enters a segment |
 | \`segment_exit\` | \`segmentId: string\` | Fires when a contact exits a segment |