Skip to content

fix(metadata-protocol): insertManyData reports the dropped-field union at BATCH level instead of naming rows it cannot identify #24171

fix(metadata-protocol): insertManyData reports the dropped-field union at BATCH level instead of naming rows it cannot identify

fix(metadata-protocol): insertManyData reports the dropped-field union at BATCH level instead of naming rows it cannot identify #24171

Triggered via pull request September 11, 2026 14:34
Status Success
Total duration 57s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
0s
Check PR Size
Check Changeset
52s
Check Changeset
Auto Label
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/17290-insertmany-dropped-fields-name-no-row.md#L0
ADR-0087 exemption (no-migration-prescription): nothing authored or stored moves: no authorable key, no Zod schema and no stored `sys_metadata` shape changes — `packages/spec` declares no response schema for this face at all, so `objectstack migrate meta` has nothing to visit, `spec-changes.json` has nothing to project and the upgrade guide gains no row. What moves is one optional member on an inline TypeScript response type of a runtime protocol method, and the channel that reaches every affected consumer is the compiler at their own call site, which names the site more precisely than a ledger line could. The `packages/spec` file in this diff is a `.describe()` STRING — customer-facing prose that this change would otherwise leave false — not a schema, a key or an accept set; nothing it declares moves.