Skip to content

feat(spec)!: a tree field's reference, when present, must name the declaring object — refused at parse otherwise (#14892) #21627

feat(spec)!: a tree field's reference, when present, must name the declaring object — refused at parse otherwise (#14892)

feat(spec)!: a tree field's reference, when present, must name the declaring object — refused at parse otherwise (#14892) #21627

Triggered via pull request September 5, 2026 22:12
Status Success
Total duration 48s
Artifacts

pr-automation.yml

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

Annotations

1 notice
Check Changeset: .changeset/tree-reference-self-only.md#L0
ADR-0087 exemption (no-migration-prescription): No authorable key is renamed, retired or re-typed: `reference` keeps its name, its type and its optionality on a `tree` field, and every self-referencing or reference-less `tree` parses byte-identically to before. What is newly refused is a `tree` whose `reference` names a different object — a shape no prose surface ever documented, that no runtime reader consumed as a cross-object link, and whose one in-repo author (the showcase field zoo) hedged in its own label. The remedy is authoring intent, not a mechanical rewrite: the author decides whether the field is this object's own hierarchy (a self-reference, or no `reference` at all) or a link to another object (a `lookup`), so `objectstack migrate meta` has nothing to rewrite and this changeset carries no rewrite instructions.