From 1ccff6f5009543e16b1e365d27422de222641cca Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 26 Oct 2026 07:02:04 +0000 Subject: [PATCH] docs(changeset): 25610 notify email-field note: delivery ships in the same release (#25754) Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_01BPTrzMQwkEcdhpQaa8xuRj --- .changeset/25610-notify-email-field-recipient.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.changeset/25610-notify-email-field-recipient.md b/.changeset/25610-notify-email-field-recipient.md index 2e8f4685d2a..ec7678fa98c 100644 --- a/.changeset/25610-notify-email-field-recipient.md +++ b/.changeset/25610-notify-email-field-recipient.md @@ -22,7 +22,7 @@ A `notify` node's `recipients` takes a fourth form, as the whole value: `{ email - The form is the whole `recipients` value, never a list entry. - `@objectstack/lint` refuses, at `os validate`, `os lint`, `os build` and the runtime publish door for a flow, an email-field recipient whose field the trigger object does not declare (`notify-email-field-unknown`), one whose field is not `email`-typed (`notify-email-field-not-email`), and one in a flow that hands its run no record of a known object — a schedule, an inbound api call, a record trigger that names no object (`notify-email-field-no-trigger-record`). A trigger object another package declares is not judged. -This change is the protocol half. Delivery — resolving the field to an address, the outbound mail configuration, the per-address rate limit and the messaging-log entry — is the messaging service's half and lands separately; until it does, a run that reaches such a node fails at the node. +This change is the protocol half. Delivery — resolving the field to an address, the outbound mail configuration, the per-address rate limit and the messaging-log entry — ships in the same release in `@objectstack/service-automation`. Clause-②: yes (widening)