Skip to content

feat(client, rest): bind both getHistory exits to HistoryMetaItemResponse; ledger row names the schema #22466

feat(client, rest): bind both getHistory exits to HistoryMetaItemResponse; ledger row names the schema

feat(client, rest): bind both getHistory exits to HistoryMetaItemResponse; ledger row names the schema #22466

Triggered via pull request September 7, 2026 21:59
Status Failure
Total duration 55s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
15s
Check PR Size
Check Changeset
51s
Check Changeset
Auto Label
17s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Check Changeset
Process completed with exit code 1.
Check Changeset: .changeset/history-door-schema-rebind.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing here is reachable by `objectstack migrate meta`: no spec property, metadata key, accepted value or exported symbol is retired, `packages/spec` is not touched at all, and no stored metadata changes shape. The affected party is a TypeScript consumer and the delivery channel is the compiler at their own call site; the remedy is a null check on `actor`, which is application code rather than a metadata migration. `type-surface-only` is deliberately NOT claimed: its predicate 4 admits a narrowing that starts from `any`, `unknown` or no annotation, and while the scoped exit is exactly that case, the unscoped exit starts from a CONCRETE inline object type whose members change — the case that category's header names as outside its class.