Skip to content

feat(spec)!: composeStacks objectConflict: 'merge' refuses object pairs whose object-level collections cannot be merged (#14848) #21672

feat(spec)!: composeStacks objectConflict: 'merge' refuses object pairs whose object-level collections cannot be merged (#14848)

feat(spec)!: composeStacks objectConflict: 'merge' refuses object pairs whose object-level collections cannot be merged (#14848) #21672

Triggered via pull request September 5, 2026 23:42
Status Success
Total duration 47s
Artifacts

pr-automation.yml

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

Annotations

1 notice
Check Changeset: .changeset/compose-merge-refuses-object-collections.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable is renamed, retired or re-typed: every object key, every `composeStacks` option and the `ConflictStrategySchema` enum (`'error' | 'override' | 'merge'`) parse exactly as before, so `objectstack migrate meta` has nothing to rewrite. What narrows is the ACCEPT SET of one option value at composition time — two stacks whose same-name objects both declare an object-level collection with different values are now refused under `'merge'` where they used to compose with the earlier stack's entries silently dropped. The refusal text carries the whole prescription (declare the collection in one stack, make the declarations identical, or use `'override'`), and the repository measures zero non-test call sites passing `objectConflict` at all (see below), so there is no stored artifact and no authored file for a migration to act on.