Skip to content

fix(trigger-record-change): decouple the flow-facing record from the batch payload #20943

fix(trigger-record-change): decouple the flow-facing record from the batch payload

fix(trigger-record-change): decouple the flow-facing record from the batch payload #20943

Triggered via pull request September 4, 2026 17:20
Status Success
Total duration 51s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
20s
Check PR Size
Check Changeset
47s
Check Changeset
Auto Label
13s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/flow-record-decoupled-from-batch-payload.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing metadata-shaped moves: no spec key, no Zod schema, no `packages/spec` declaration, no export, no config field and no stored row changes spelling or shape, and a stored flow definition is byte-identical before and after — `objectstack migrate meta` has nothing to reach. What moves is the reference identity of the object one runtime seam hands a flow. The consumer note below names the supported node for writing a record; it prescribes no rewrite of any authored artifact, and the code it could affect is a stack author's own registered function body, which the metadata upgrader cannot see.